On Mon, Sep 15, 2008 at 01:13:28PM -0500, [EMAIL PROTECTED] wrote: > > The big takeaway here is that while copies=N guarantees there will be N > copies of blocks, it _does not_ guarantee that they will always be on > separate disks. If you lose a disk there is still a chance that you lose > the pool. zraid(2) > copies=N >
It's also worth pointing out that ZFS currently doesn't survive toplevel vdev failure. If it happens while the pool is up, it will enter the I/O failure state when trying to write the labels, despite the fact it could theoretically continue on with the rest of the vdevs. If it happens while the pool is exported or the system is down, it treats this like the root vdev is faulted. Both of these are bugs that are being worked on - the only reason a pool should be faulted is because critical pool-wide metadata is not available. - Eric -- Eric Schrock, Fishworks http://blogs.sun.com/eschrock _______________________________________________ storage-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/storage-discuss
