>>>>> "re" == Richard Elling <[EMAIL PROTECTED]> writes: >>>>> "tb" == Tom Bird <[EMAIL PROTECTED]> writes:
tb> There was a problem with the SAS bus which caused various
tb> errors including the inevitable kernel panic, the thing came
tb> back up with 3 out of 4 zfs mounted.
re> In general, ZFS can only repair conditions for which it owns
re> data redundancy.
If that's really the excuse for this situation, then ZFS is not
``always consistent on the disk'' for single-VDEV pools.
There was no loss of data here, just an interruption in the connection
to the target, like power loss or any other unplanned shutdown.
Corruption in this scenario is is a significant regression w.r.t. UFS:
http://mail.opensolaris.org/pipermail/zfs-discuss/2008-June/048375.html
How about the scenario where you lose power suddenly, but only half of
a mirrored VDEV is available when power is restored? Is ZFS
vulnerable to this type of unfixable corruption in that scenario,
too?
pgpcFzodF6Qa6.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
