On Wed, Jun 11, 2008 at 10:43:26PM -0700, Richard Elling wrote: > > AFAIK, SVM will not handle this problem well. ZFS and Solaris > Cluster can detect this because the configuration metadata knows > the time difference (ZFS can detect this by the latest txg).
Having been through this myself with SVM in the past, no, it does not handle this well at all. If I remember correctly Veritas handled this a lot better than SVM did/does (please bear in mind I haven't used either of those in quite some time). > I predict that if you had booted from disk B, then it would have > worked (but I don't have the hardware setup to test this tonight) Unfortunatly I thought of this after deleting his mail. He said that before pulling disk B he scrambled it with dd. He broke the boot sectors on disk B, which ZFS doesn't replicate as far as I can tell. (See the section on ZFS install where it talks about adding a mirror after the fact, you need to manually install the boot sectors.) IMHO, ZFS boot/root should really go out of its way to make sure the boot sectors are up to date. As most other mirroring solutions (hardware or software) mirror raw volumes, they just do it automatically due to the nature of how they work. This is behavior that has come to be expected, so it's a really good idea if ZFS could do it. I think something else that might help is if ZFS were to boot, see that the volume it booted from is older than the other one, print a message to that effect and either halt the machine or issue a reboot pointing at the other disk (probably easier with OF than the BIOS of a PC). -brian -- "Coding in C is like sending a 3 year old to do groceries. You gotta tell them exactly what you want or you'll end up with a cupboard full of pop tarts and pancake mix." -- IRC User (http://www.bash.org/?841435) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
