Robert Milkowski wrote:
Miles Nordin wrote:
"csb" == Craig S Bell <cb...@standard.com> writes:
csb> Two: If you lost data with another filesystem, you may have
csb> overlooked it and blamed the OS or the application,
yeah, but with ZFS you often lose the whole pool in certain
classes of
repeatable real-world failures, like hotswap disks with flakey power
or SAN's without NVRAM where the target reboots and the initiator
does
not. Losing the whole pool is relevantly different to corrupting
the
insides of a few files.
I think that most people including ZFS developers agree with you that
losing an access to entire pool is not acceptable. And this has been
fixed in snv_126 so now in those rare circumstances you should be able
to import a pool. And generally you will end-up in a much better
situation than with legacy filesystems + fsck.
Just a slight correction. The current build in-process is 128 and that's the
build into which the changes were pushed.
-tim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
