> Still, after reading Mathias's description, it seems that the former > node is doing an implicit forced import when it boots back up. This > seems wrong to me. > > zpools should be imported only of the zpool itself says it's not already > taken, which of course would be overidden by a manual -f import.
The problem (Danger: I'm completely going on assumptions here) is that this locking is almost always some sort of "dirty" or "locked" flag. So if your server crashes, you *want* the host to re-import the dirty pool at boot. Otherwise every unclean shutdown is a manual intervention. So a simple 'dirty/clean' flag isn't enough information and I'm assuming that's all the -f is checking for today. I believe that VxVM gets around this by forcing the import at boot only if the hostid of the machine matches the hostid on the group. > <zpool> "sorry, i already have a boyfriend, host b" > <host a> "darn, ok, maybe next time" And it's the lack of "host b" information in the pool that prevents this at the moment.. <host a> "Hey, let's go!" <zpool> "Huh, I thought I was already seeing someone?" <host a> "Yeah, me! Now let's go!" <zpool> "Wow, really? Okay." -- 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
