Every year PGCon holds a charity auction as part of the closing session. All proceeds go to The Ottawa Mission, a local group. The auction includes items you would keep as art, and some you would consume before you left town. Others, such as empty paper bags or cardboard boxes are left in the recycling bin. It is all in good fun. 1 Chocolate from Japan $20.00 2 Elephant with cloud $220.00 3 […]
PGCon 2016 charity auction Read More »
Let’s try the speed test which comes with Bacula’s btape utility. This is Bacula 7.4.0 on FreeBSD 10.2, with a Dell TL4000 LTO-4 tape library.
Using Bacula’s btape speed test on FreeBSD 10.2 and an LTO-4 tape drive Read More »
I have recently added two 480 GB SSDs to a 10 x HDD raidz2 system. The SSDs will be mainly used for spooling to tape during backups, but I’m going to use a small part of it for a SLOG. Not all systems benefits from a SLOG (Separate intent LOG), but synchronous writes, such as databases, do. All ZFS systems have a ZIL (ZFS Intent Log); it is usually part of the zpool.
Adding SLOG to a zpool Read More »
For future reference, this is the knew server. It runs a few jails, including Bacula regression testing services. File systems Paritions zpools /var/run/dmesg.boot
Last night, I moved a SAS card and had to renumber some devices. I also moved two SSDs into the same box (see photos). Those SSDs were the boot drives from the system from which I pulled the SAS drive. That box, tape01, contains the Bacula configuration file I need for this new box. I know, I know. Why not use Bacula to restore that file. That would be too easy. I want
Importing a zpool and renaming it Read More »
Last night, I added a SAS card into a box which is connected to a tape library (photos here). After starting up the box, Nagios reported that the tape device was no longer present. I first added such checks back in 2012 and updated them for more recent acquisitions. This means that the copy-to-tape jobs did not run last night, because there was no sa0, instead, there was an sa1, which was not
Adding in a SAS card renumbered my devices Read More »
I do have a FreeBSD-11 box, cuppy: $ uname -a FreeBSD cuppy.int.unixathome.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r279394: Sat Feb 28 21:01:21 UTC 2015 dan@cuppy.unixathome.org:/usr/obj/usr/src/sys/GENERIC amd64 $ That box is used mostly for testing and/or erasing DLT tapes. The current status of that box is not healthy. It’s running fine, but it is not optimal: Let’s fix this. Background Why is one drive upset? Because I installed FreeBSD onto it. Why? I don’t know,
Adding a failed HDD back into a ZFS mirror Read More »
In this post, I am working with FreeBSD 10.2 on this server. Over the past few days, a 3 year old drive has been giving errors. The number of errors has been constant, but I have a spare drive here, so I decided to replace it. I have verified that it is out of warranty. Rather than pull the error drive and replace it, I opted to add in a new drive and
Added new drive when existing one gave errors, then zpool replace Read More »
That smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors problem which arose on Sunday is still around. I’ve run a short test, a long test, and a ZFS scrub is now underway. I may just replace the drive. $ sudo smartctl -P show /dev/ada0 smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.2-RELEASE-p9 amd64] (local build) Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org Drive found in smartmontools Database. Drive identity strings: MODEL: TOSHIBA DT01ACA300 FIRMWARE:
smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors persists Read More »
This morning I discovered this in my logs: Feb 14 04:56:39 knew kernel: (ada0:ata0:0:0:0): READ_DMA48. ACB: 25 00 b8 a8 f0 40 4b 00 00 00 e8 00 Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): CAM status: ATA Status Error Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 40 (UNC ) Feb 14 04:56:54 knew kernel: (ada0:ata0:0:0:0): RES: 51 40 58 a9 f0 4b 4b 00 00 48 00
smartd: Device: /dev/ada0, 8 Currently unreadable (pending) sectors Read More »