On Tue, 15 May 2007, Trevor Watson wrote: > I don't suppose that it has anything to do with the flag being "wm" > instead of "wu" on your second drive does it? Maybe if the driver thinks > slice 2 is writeable, it treats it as a valid slice?
If the slice doesn't take up the *entire* disk, then it doesn't count as the backup slice. > > I still get the same error message, one difference I see between the > > drives is one (with the error) has > > > > 2 backup wu 0 - 38911 298.08GB (38912/0/0) 625121280 > > 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) 522369540 > > > > and the other > > > > 2 backup wm 0 - 38909 298.07GB (38910/0/0) 625089150 > > 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) 522369540 If these are the same disk size, then both slice 2's should end at 38911. See the dm_isoverlapping() function in libdiskmgt: http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libdiskmgt/common/entry.c#563 The overlap checking starts around line 680+. Regards, markm _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
