Hi, Unfortunately, every now and then someone has his zpool corrupt, with no tools to fix it! This is due to either zfs bugs, or hardware lying about whether the bits really hit the platters. I am evaluating what I should be using for storing VMware ESX VM images (ext3 or zfs on NFS). I really really want zfs snapshots, but loosing the pool is going to be a royal pain for small businesses.
My questions are: 1- What are the best practices to avoid pool corruption (even if it incurs a performance hit) ? 2- I remember a suggested idea that zfs would iterate back in time when mounting a zpool till it finds a fully written pool and uses that, thus avoiding corruption. Is there an RFE for that yet ? I'd like to subscribe to that, and I might even delay jumping on the zfs wagon till it's got this recovery feature! Regards
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
