Hot answers tagged zfs
I'm using ZFS with non-ECC RAM. Widely enough. I'm not writing this to say it's safe. However, for several years I didn't see zfs corruption yet. Furthermore, when using zfs on ancient hardware, I saw all sort of memory problems, even an inability to boot up. From my experience - you will encounter all sorts of fatal kernel traps faster than the zfs data ...
The problem is zfs's error correction features (checksum & scrub) can potentially result in a total loss of data on a memory corruption error as opposed to say xfs which will happily write your error to disk in just the affected block(s).
option - when you want to stay with FreeBSD, check FreeNAS to automate complexity you are afraid of. option - NexentaStor, it is Solaris based storage appliance SW with great management web gui. Up to 18TB setup is for free. Again there you can easily manage complex zfs send|receive vs. a lot of datasets configuration. If you have speedy lines between ...
Basicly there is no official way to recover other than restore from backup. But there is ZFS feature called rewind, that may be possible to remove transactions from the pool to a point that the pool is functional again. The following text is from ZFS Internals blog part #11 DO NOT TRY IT IN PRODUCTION. USE AT YOUR OWN RISK! zpool import -FX mypool ...
Only top voted, non community-wiki answers of a minimum length are eligible