eric kustarz wrote: > > On Sep 21, 2007, at 3:50 PM, Tim Spriggs wrote: > >> m2# zpool create test mirror iscsi_lun1 iscsi_lun2 >> m2# zpool export test >> m1# zpool import -f test >> m1# reboot >> m2# reboot > > Since I haven't actually looked into what problem caused your pools to > become damaged/lost, i can only guess that its possibly due to the > pool being actively imported on multiple machines (perhaps even > accidentally). > > If it is that, you'll be happy to note that we specifically no longer > that to happen (unless you use the -f flag): > http://blogs.sun.com/erickustarz/entry/poor_man_s_cluster_end > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6282725 > > Looks like it just missed the s10u4 cut off, but should be in s10_u5. > > In your above example, there should be no reason why you have to use > the '-f' flag on import (the pool was cleanly exported) - when you're > moving the pool from system to system, this can get you into trouble > if things don't go exactly how you planned. > > eric
That's a very possible prognosis. Even when the pools are exported from one system, they are still marked as attached (thus the -f was necessary). Since I rebooted both systems at the same time I guess it's possible that they both made claim to the pool and corrupted it. I'm glad this will be fixed in the future. -Tim _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
