zap
zap copied to clipboard
WAS NOT DESTROYED because its expiration time could not be determined. /root/zap/zap: 162: bc: not found
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-07T19:27:10p0000--1d
should be deleted as it's now more than 1D old but I am facing the following errors
/root/zap/zap destroy or /root/zap/zap destroy HOSTNAME both display
WARN: SNAPSHOT zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-07T19:27:10p0000--1d WAS NOT DESTROYED because its expiration time could not be determined.
/root/zap/zap: 162: bc: not found
WARN: SNAPSHOT zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T20:00:01p0000--1d WAS NOT DESTROYED because its expiration time could not be determined.
/root/zap/zap: 162: bc: not found
WARN: SNAPSHOT zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T21:00:01p0000--1d WAS NOT DESTROYED because its expiration time could not be determined.
/root/zap/zap: 162: bc: not found
WARN: SNAPSHOT zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T22:00:01p0000--1d WAS NOT DESTROYED because its expiration time could not be determined.
/root/zap/zap: 162: bc: not found
WARN: SNAPSHOT zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T23:00:01p0000--1d WAS NOT DESTROYED because its expiration time could not be determined.
/root/zap/zap: 162: bc: not found
zfs list -t snapshot
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-07T19:27:10p0000--1d 6.62M - 13.7G -
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T20:00:01p0000--1d 2.90M - 13.7G -
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T21:00:01p0000--1d 3.18M - 13.7G -
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T22:00:01p0000--1d 5.48M - 13.7G -
zfs/backups/vm-105-disk-0@ZAP_HOSTNAME_2023-01-08T23:00:01p0000--1d 0B - 13.7G -
Issue was bc calculator was missing
apt install bc
Hello @hellomotow. Sorry for the delay. I've done some testing on GNU/Linux systems and will tweak a few things based on what I found. For example, I hope I can find alternatives to utilities like bc
or hostname
that might not be installed there by default.