For the last four years I've been successfully using a script to make daily incremental backups to a USB hard drive using zfs send/receive. The script imports the backup pool for the duration of the backup with
There was no further info in any logs apart from the following in the console log:
The script checks the status of all pools with
This isn't a major disaster because I can recreate the backup pool and send a new replication dataset but I'm concerned that it's possible that an entire pool can so easily be silently destroyed and I'm interested to know what could be the possible causes and what can be done to minimise the risk of it happening again.
zpool import -N -o cachefile=none m3
. Last night the script failed with the message:
Code:
cannot import 'm3': I/O error
Destroy and re-create the pool from
a backup source
Code:
Feb 15 20:11:58 curlew kernel: Feb 15 20:11:58 curlew ZFS[20269]: failed to load zpool $m3
Feb 15 20:11:58 curlew kernel: Feb 15 20:11:58 curlew ZFS[20279]: failed to load zpool $m3
zpool status
immediately before exporting the backup pool on completion and reports any problems so whatever caused this problem must have occurred as the pool was exported the previous night or as soon as attempting to import it at the start of the script because the drive was disconnected and powered down during the intervening time.This isn't a major disaster because I can recreate the backup pool and send a new replication dataset but I'm concerned that it's possible that an entire pool can so easily be silently destroyed and I'm interested to know what could be the possible causes and what can be done to minimise the risk of it happening again.