Yesterday, I started a zpool replace. It finished overnight, and dropped the suspect drive out of the vdev. The resilver finished in the middle of the night: As you can see, da22p1 has taken the place of da17p1. The resilver took As the new drive is being resilvered, I started looking at metrics. Here is […]
The replacement – a followup Read More »
In this post I will replace a working, but suspect, drive with another drive. No down time. The server is knew. In this post: FreeBSD 12.2 ZFS TOSHIBA MD04ACA500 5TB drive – the suspect drive: da17 TOSHIBA HDWE150 5TB drive – the replacement: da22 None of these drives are under warranty What drives are in
Replacing a failing drive in a ZFS zpool Read More »
It is time to replace /dev/da17 in knew. The replacement drive is also documented. The replacement procedure has also been documented. An upcoming blog post will document the replacement. I’m seeing these messages: Dec 12 09:23:03 knew smartd[2124]: Device: /dev/da17 [SAT], 40 Currently unreadable (pending) sectors Dec 12 09:53:04 knew syslogd: last message repeated 1
smartctl output TOSHIBA MD04ACA500 653AK2MXFS9A Read More »
I have these boot drives, I want to copy them to another. They both happen to be zroot and bootable. I booted from mfsBSD and imported both new and old zroot, using the pool ID shown by zpool import -N. root@mfsbsd:~ # zpool import -N pool: data01 id: 2668514456528412656 state: ONLINE action: The pool can
Duplicating a zpool Read More »
In this post, I am creating a 4 drive ZFS pool consisting of two mirror. In this post: I’m booting from mfsBSD 12.1 ZFS Creating partitions On FreeBSD, it is convention to create partitions. It is not necessary, but I don’t use all the space in case a future replacement drive is slightly smaller than
Creating a 4 drive ZFS zpool: stripe over mirrors Read More »
ZFS has a the ability to share itself within a jail. That gives the jail some autonomy, and I like that. I’ve written briefly about that, specifically for iocage. More recently, I started using a zfs snapshot for caching clearing. The purpose of this post is to document the existing configuration of the production FreshPorts
Changing from one dataset to another within a FreeBSD [iocage] jail Read More »
I am replacing one zroot with another because of missing binaries and suspect layout. The existing zroot is an old system predating current zroot layouts. This work is being performed on a test system (that link is not safe for young eyes). In this post: FreeBSD 12.1 mfsBSD 12.1 The failed attempt I tried once,
Renaming and replacing zroot filesystems using mfsBSD Read More »
Today I was updating some servers. One of them was rebooted three times. On the third time, one of the drives went missing. This is how I tracked down which drive, and which slot in the server, and fixed it. I’m writing it mostly so I can remember how to flash the light on the
ZFS: adding a drive back into the zpool Read More »
I’m in the final stages of the FreshPorts packages project. One of the last tasks is clearing the packages cache from disk when new package information is loaded into the database. See also: Clearing the packages cache ZFS when you’re not doing ZFS Several of the configuration items have been learned from putting my poudriere
using zfs rollback for cache clearing Read More »
This is just a placeholder for me to find this later. I was cleaning up some old snapshots. I’m not sure I should have removed those snapshots and I’m saving this here for next time I use bectl. [dan@slocum:~] $ grep -v autosnap ~/tmp/snapshots/snapshots zroot/bootenv/default@2020-01-11-18:16:51 zroot/bootenv/default/tmp@2020-01-11-18:16:51 zroot/bootenv/default/usr@2020-01-11-18:16:51 zroot/bootenv/default/usr/local@2020-01-11-18:16:51 zroot/bootenv/default/usr/obj@2020-01-11-18:16:51 zroot/bootenv/default/usr/src@2020-01-11-18:16:51 zroot/bootenv/default/var@2020-01-11-18:16:51 zroot/bootenv/default/var/audit@2020-01-11-18:16:51 zroot/bootenv/default/var/empty@2020-01-11-18:16:51 zroot/bootenv/default/var/log@2020-01-11-18:16:51 zroot/bootenv/default/var/tmp@2020-01-11-18:16:51