These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
But I still have about 40 hourly snapshots of each dataset, and 250 in total, which indicates that sanoid is still running the default config. The permissions on /etc/sanoid/sanoid.conf are the same as the defaults:
I am also using the systemd timer. It just occurred to me as I was writing this to try restarting the sanoid.service, but I don't think I will know if it worked until 15 minutes from now. I never saw anything about it in the documentation, so I doubt this will solve the problem. Any other ideas?
I created my config file to be much less active than the defaults:
But I still have about 40 hourly snapshots of each dataset, and 250 in total, which indicates that sanoid is still running the default config. The permissions on
/etc/sanoid/sanoid.conf
are the same as the defaults:I am also using the systemd timer. It just occurred to me as I was writing this to try restarting the sanoid.service, but I don't think I will know if it worked until 15 minutes from now. I never saw anything about it in the documentation, so I doubt this will solve the problem. Any other ideas?