Migration from the KQ Implementation
Jason J. W. Williams
jasonjwwilliams at gmail.com
Wed May 4 21:05:11 EDT 2011
> Snapshots won't do you any good if the pool is damaged in an unfortunate way
> that stops it from reassembling.
> Backups are of paramount importance, sure, but fsck is important, too,
> especially when a fsck pass might take 10 minutes vs. 2 days for restoring
> all the data from a backup (and the inevitable loss of anything since the
> last backup.
The question is what are expecting a ZFS fsck to do? Rollback to an
earlier consistent form of the filesystem? By default ZFS attempts
that already. For situations where the hardware controller outright
lies to the OS about what it's doing and causes corruption, PSARC
2009/479 (aka zpool recovery) attempts to clear out as many bad
transaction groups as it can to return the pool to a consistent
mountable state. So that's really question...beyond those things what
would a ZFS fsck do that wouldn't require a custom recovery job?
More information about the zfs-discuss