On Jul 24, 2009, at 22:17, Bob Friesenhahn wrote:
A journaling filesystem uses a journal (transaction log) to roll
back (replace with previous data) the unordered writes in an
incomplete transaction. In the case of ZFS, it is only necessary to
go back to the most recent checkpoint and any subsequent writes
after that checkpoint are simply forgotten.
And fixing CR 6667683 is what would allow ZFS to properly /
automatically recover from a messed up power down:
need a way to rollback to an uberblock from a previous txg
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6667683
Most of the issues that I've read on this list would have been
"solved" if there was a mechanism where the user / sysadmin could tell
ZFS to simply go back until it found a TXG that worked.
The trade off is that any transactions (and their data) after the
working one would be lost. But at least you're not left with an un-
importable pool.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
