slocum
This post has been replaced by a newer one. For future reference, this is the slocum server, which I use for various jails and services:
This post has been replaced by a newer one. For future reference, this is the slocum server, which I use for various jails and services:
Today it finished. That ZFS send I started on Monday finally finished. Recap The original command was: # zfs send storage/compressed/bacula@2013.07.22:06:33 | mbuffer | ssh -t dan@10.5.0.20 ‘zfs receive system/usr/local/bacula/FromKraken’ That’s was the initial send of the filesystem. But more data has been added to it. So I take another snapshot, and send that: Send what’s accumulated since previous send # zfs snapshot storage/compressed/bacula@2013.07.25:08:20 And now I send the incremental stream: # zfs
zfs send | zfs receive; finally finished Read More »
THe last system I set up with ZFS, I used a script. Today, when trying a system with different device types, I encountered a limitation of that script. I need to fix it. In the above script, NUM takes on the value of what digits appear in the string of I. Given that DISKS contains both ada0 and da0, two disks will get the same value for $I. That’s a problem. I need
Problem with disk numbering in my ZFS creation script Read More »
I was trying to recompile sysutils/bacula-client on a FreeBSD 8.4 jail when I encountered some perplexing link errors. It took me a while to figure it out, but with the help of some IRC conversation, we figured it out. I started off by deleting the old (quite old) port: bacula-client-5.0.3 Then I recompiled: cd /usr/ports/sysutils/bacula-client && make install clean The errors in question are: I tried recompiling a few ports, such as gettext.
Compiling bacula client gives link errors Read More »
One of the challenges of providing hands-on demonstrations is giving everyone their own sandbox to play in. I don’t want people to spend time on installing software. I want people to learn about the software in question, specifically Bacula. With this in mind, I’ve been building up a solution based on FreeBSD 9.1, ZFS, and jails. My solution is pretty nifty, but I don’t think it’s anything special. The key is simplicity. The
The Bacula Tutorial jail server Read More »
I’m about to start setting up a ZFS-only box using FreeBSD 8.2. There will be no UFS volumes in this system. Every previous server I have set up has always booted from a gmirror’d UFS system first, then mounted a ZFS array. This time, everything will be on ZFS. I’ve described this server previously when I first chose the parts back in January. Now, the push is on to get this system installed
Creating a ZFS-only box – the first look Read More »
About a week ago, I was doing some HDD benchmark tests and I accidentally specified the boot drive as the source for a test. Oops. Everything was OK. Until I rebooted. It would not boot. I figured I knew what happend. I’d munged my boot code. And I knew how to fix it. However, I didn’t realize that I’d also deleted the boot partition. I asked on the FreeBSD dev IRC channel. db
Oops, I deleted my boot partition Read More »
Wyze uses this tuning on his 2GB NAS box. # Dynamically adjust write limit based on previous txg commits to attempt # to maintain a 2-second commit time vfs.zfs.txg.synctime_ms=”2000″ # Set a minimum write limit of 50MB which is slightly more than the default vfs.zfs.write_limit_min=”50M” # Default vfs.zfs.write_limit_shift appears to be “3” which on a system # with 2GB RAM such as this one results in a write_limit_max of 256MB, which # is
I think I’m now at the point where I have all the hardware assembled and it’s ready for testing. Now I’m trying to determine what set of fio tests to run. If you know of a set of standard tests, or just have some of your own, please let me know in the comments. The hardware The disks I have assembled are all available via the LSI 9211-8i. The basic hardware specs are:
The hardware is ready. What tests to run? Read More »
I’m getting very slow throughput on these drives during my first set of tests. I have no idea why… The drive in question is: $ grep ada2 /var/run/dmesg.boot ada2 at ahcich4 bus 0 scbus5 target 0 lun 0 ada2: <ST2000DM001-1CH164 CC24> ATA-8 SATA 3.x device ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada2: Command Queueing enabled ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad12 Here
Testing the benchmark scripts – 1 Read More »