So much for the "it's a consumer hardware problem" argument. I for one gotta count it as a major drawback of ZFS that it doesn't provide you a mechanism to get something of your pool back in the manner of reconstruction or reversion, if a failure occurs, where there is a metadata inconsistency.
A policy of data integrity taken to the extreme of blocking access to good data is not something OS users want. Users don't put up with this sort of thing from other filesystems... some sort of improvement here is sorely needed. ZFS ought to be retaining enough information and make an effort to bring pool metadata back to a consistent state, even if it means loss of data, that a file may have to revert to an older state, or a file that was undergoing changes may now be unreadable, since the log was inconsistent.. even if the user should have to zpool import with a recovery-mode option or something of that nature. It beats losing a TB of data on the pool that should be otherwise intact. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
