ZFS is a very reliable file system. At some point ZFS will give up and say "I cannot reliably save bits."
It is your hardware where the unreliability lies and ZFS detects that. Would you rather prefer silent corruption?
It is your hardware where the unreliability lies and ZFS detects that. Would you rather prefer silent corruption?
Otherwise the feature set seems great: both a volume manager and a file system, seamless compression, deduplication, COW and snapshots - what's not to love :)
But there is. It's `zpool clear <poolname>`.
That said, you probably need to have created or imported the pool using stable device names (e.g. `zpool import -d /dev/disk/by-id` or `by-part-uuid`, for example). Otherwise, when reattaching the USB device it might get assigned a different device name (e.g. `/dev/sdb` instead of `/dev/sda`) and ZFS might think the device is still unavailable.