This morning I noticed this in the logs after doing some pkg upgrade. I was mainly updating openvpn, but in that operation, fail2ban was removed (because I went from python312 to python314). I noticed it missing on one host: I ran this grep to verify fail2ban had been removed from another host: Well, this host doesn’t run fail2ban, but those messages are “interesting”. How much is nvme mentioned in the logs? [12:31 r730-01 […]
This post will be short on detail. I’m writing it for myself, to document what I’m doing. I suspect Migrating data02/freshports/dev-ingress01 to another zpool will be more useful to you. In this post: FreeBSD 15.0 I stopped the jail: [15:30 r730-01 dvl ~] % sudo service jail stop dev-nginx01 Stopping jails: dev-nginx01. I took dev.freshports.org offline via: [15:32 r720-02-proxy01 dvl ~] % ~/bin/offline dev.freshports.org "$(date -R -v +2H)" "Offline for filesystem migration" <html>
migrating data02/freshports/dev-nginx01 to data04 Read More »
Now that I’ve copied two filesets from one zpool to another, let’s delete old snapshots. In this post: FreeBSD 15.0 Freeing up space I’m still hesitant to delete original data, but I’ll delete the snapshots. Here’s my list: [20:25 r730-01 dvl ~] % zfs list -H -o name -r -t snapshot data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15 | grep -v for.data04.0 | less data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-15_00:00:03_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-16_00:00:16_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_00:00:07_daily data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_19:00:02_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_20:00:02_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_21:00:09_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_22:00:09_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/dvl-src@autosnap_2026-04-17_23:00:11_hourly … data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:15:13_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:30:02_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_19:45:11_frequently data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_20:00:01_hourly data02/freshports/dev-ingress01.DELETE.ME.after.2026.05.15/scripts@autosnap_2026-04-19_20:00:01_frequently That
Cleaning up snapshots Read More »
Earlier today, I moved two file systems from one zpool to another. I use sysutils/sanoid to take and manage snapshots of the more important data. In this post, I’ll update that configuration. Migrating ZFS filesystems from one zpool to another – same host Migrating data02/freshports/dev-ingress01 to another zpool These are the items which need updates: [20:04 r730-01 dvl ~] % sudo cp -p /usr/local/etc/sanoid/sanoid.conf /usr/local/etc/sanoid/sanoid.conf.backup.2026.04.19 [20:08 r730-01 dvl ~] % sudoedit /usr/local/etc/sanoid/sanoid.conf [20:03
after moving datasets, adjust configuration for sanoid and others Read More »
I’m going to migrate data02/freshports/dev-ingress01 to the data04 This is before: [13:45 r730-01 dvl ~] % zfs list -r data02/freshports/dev-ingress01 NAME USED AVAIL REFER MOUNTPOINT data02/freshports/dev-ingress01 229G 60.6G 88K none data02/freshports/dev-ingress01/dvl-src 197G 60.6G 197G /jails/dev-ingress01/usr/home/dvl/src data02/freshports/dev-ingress01/freshports 22.9G 60.6G 2.09G /jails/dev-ingress01/var/db/freshports data02/freshports/dev-ingress01/freshports/cache 2.30M 60.6G 132K /jails/dev-ingress01/var/db/freshports/cache data02/freshports/dev-ingress01/freshports/cache/html 2.07M 60.6G 2.07M /jails/dev-ingress01/var/db/freshports/cache/html data02/freshports/dev-ingress01/freshports/cache/spooling 104K 60.6G 104K /jails/dev-ingress01/var/db/freshports/cache/spooling data02/freshports/dev-ingress01/freshports/message-queues 20.8G 60.6G 14.4M /jails/dev-ingress01/var/db/freshports/message-queues data02/freshports/dev-ingress01/freshports/message-queues/archive 20.8G 60.6G 11.7G /jails/dev-ingress01/var/db/freshports/message-queues/archive data02/freshports/dev-ingress01/ingress 5.39G 60.6G 132K /jails/dev-ingress01/var/db/ingress data02/freshports/dev-ingress01/ingress/latest_commits 528K 60.6G
Migrating data02/freshports/dev-ingress01 to another zpool Read More »
Not so long ago, a disk space issue arose. I obtained some new drives (thank you to those who donated) and I consolidated some of the space. However, I had not yet taken care of the problem. For my first example, I’ll copy my vm data over. In my next post, I’ll copy dev.freshports.org to a new dataset. In this post: FreeBSD 15.0 What happened? Yesterday, the chickens came home to roost. The
Migrating ZFS filesystems from one zpool to another – same host Read More »
After zpool upgrade blocked by gpart: /dev/da0p1: not enough space, I’ve decided to create a new Azure VM, snapshot the now-faulty-drive, attach it to the host, and start zfs replication to copy the data to new drive. Or something like that. The existing drive needs to be imported with a checkpoint rollback, then copied to a drive with different partition sizes. Here’s the new host: dvl@nagios03-recovery:~ $ gpart show => 34 62984125 da0
nagios03: drive recovery Read More »
This seems to be inconvenient. Now I have to rollback to that checkpoint. [20:52 nagios03 dvl ~] % sudo zpool checkpoint zroot [20:52 nagios03 dvl ~] % sudo zpool upgrade zroot This system supports ZFS pool feature flags. Enabled the following features on ‘zroot’: redaction_list_spill raidz_expansion fast_dedup longname large_microzap block_cloning_endian physical_rewrite Pool ‘zroot’ has the bootfs property set, you might need to update the boot code. See gptzfsboot(8) and loader.efi(8) for details. [20:52
zpool upgrade blocked by gpart: /dev/da0p1: not enough space Read More »
I was getting messages like this from sanoid: cannot destroy 'data02/jails/mysql02.bad@autosnap_2026-02-10_12:00:07_hourly': snapshot has dependent clones use '-R' to destroy the following datasets: data02/jails/mysql02@mkjail-202602102333 data02/jails/mysql02@autosnap_2026-02-11_00:00:06_daily data02/jails/mysql02@autosnap_2026-02-12_00:00:09_daily data02/jails/mysql02@autosnap_2026-02-13_00:00:01_daily data02/jails/mysql02@autosnap_2026-02-14_00:00:11_daily data02/jails/mysql02@autosnap_2026-02-15_00:00:01_daily data02/jails/mysql02@autosnap_2026-02-16_00:00:02_daily data02/jails/mysql02@autosnap_2026-02-16_18:00:02_hourly data02/jails/mysql02@autosnap_2026-02-16_19:00:30_hourly data02/jails/mysql02@autosnap_2026-02-16_20:00:02_hourly data02/jails/mysql02@autosnap_2026-02-16_20:00:02_frequently data02/jails/mysql02@autosnap_2026-02-16_20:15:08_frequently data02/jails/mysql02@autosnap_2026-02-16_20:30:02_frequently data02/jails/mysql02@autosnap_2026-02-16_20:45:10_frequently data02/jails/mysql02@autosnap_2026-02-16_21:00:01_hourly data02/jails/mysql02@autosnap_2026-02-16_21:00:01_frequently data02/jails/mysql02@autosnap_2026-02-16_21:15:08_frequently data02/jails/mysql02@autosnap_2026-02-16_21:30:01_frequently data02/jails/mysql02@autosnap_2026-02-16_21:45:09_frequently data02/jails/mysql02@autosnap_2026-02-16_22:00:03_hourly data02/jails/mysql02@autosnap_2026-02-16_22:00:03_frequently data02/jails/mysql02@autosnap_2026-02-16_22:15:08_frequently data02/jails/mysql02@autosnap_2026-02-16_22:30:01_frequently data02/jails/mysql02@autosnap_2026-02-16_22:45:09_frequently data02/jails/mysql02@autosnap_2026-02-16_23:00:02_hourly data02/jails/mysql02@autosnap_2026-02-16_23:00:02_frequently data02/jails/mysql02@autosnap_2026-02-16_23:15:08_frequently data02/jails/mysql02@autosnap_2026-02-16_23:30:01_frequently data02/jails/mysql02@autosnap_2026-02-16_23:45:09_frequently data02/jails/mysql02@autosnap_2026-02-17_00:00:00_daily data02/jails/mysql02@autosnap_2026-02-17_00:00:00_hourly data02/jails/mysql02@autosnap_2026-02-17_00:00:00_frequently data02/jails/mysql02@autosnap_2026-02-17_00:15:10_frequently data02/jails/mysql02@autosnap_2026-02-17_00:30:00_frequently data02/jails/mysql02@autosnap_2026-02-17_00:45:10_frequently data02/jails/mysql02 could not remove data02/jails/mysql02.bad@autosnap_2026-02-10_12:00:07_hourly : 256 at /usr/local/bin/sanoid line 413. cannot destroy 'data02/jails/mysql02.bad@autosnap_2026-02-10_13:00:15_hourly': snapshot has
Cleaning up old snapshost: snapshot has dependent clones Read More »
Following from a recent toot, I’ve decide to expose some very personal data. aws-1 [18:50 aws-1 dvl ~] % zfs get refcompressratio -t filesystem NAME PROPERTY VALUE SOURCE data01 refcompressratio 1.00x – data01/freshports refcompressratio 1.00x – data01/freshports/ingress01 refcompressratio 1.00x – data01/freshports/ingress01/jails refcompressratio 1.00x – data01/freshports/ingress01/jails/freshports refcompressratio 1.91x – data01/freshports/ingress01/jails/freshports.14.3 refcompressratio 1.91x – data01/freshports/ingress01/jails/ports refcompressratio 1.20x – data01/freshports/ingress01/var refcompressratio 1.00x – data01/freshports/ingress01/var/db refcompressratio 1.00x – data01/freshports/ingress01/var/db/freshports refcompressratio 1.99x – data01/freshports/ingress01/var/db/freshports/cache refcompressratio 1.00x – data01/freshports/ingress01/var/db/freshports/cache/html
Show us your refcompressratio Read More »