> > > Consider a server [with] three drives, A, B, and C, in which A and B are > > > mirrored and > > > C is not. Pull out A, B, and C, and re-insert them as A, C, and B. If > > > B is slow to come up for some reason, ZFS will see "C" in place of > > > "B", and happily reformat it into a mirror of "A". (Or am I reading this > > > incorrectly?) > > Again, thanks to devids, the autoreplace code would not kick in here at > > all. You would end up with an identical pool. > > Is this because C would already have a devid?
Well, it's because all the members of the ZFS pool have information about the pool and their place in it. The path of a member isn't important. > If I insert an unlabeled disk, what happens? Nothing. If ZFS can't find a signature on it, it knows it's not part of a ZFS pool. > What if B takes five minutes to spin up? That sounds like something for FMA to deal better with. It might hang for a period of time if the driver doesn't respond quickly. > If it never does? At some point the device driver needs to respond. If the device doesn't become ready, it'll have to time out and be noted as a failure. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
