I have to drives with the same slices and I get an odd error if I try and create a pool on one drive, but not the other: Part Tag Flag Cylinders Size Blocks 0 swap wu 3 - 264 2.01GB (262/0/0) 4209030 1 root wm 265 - 2304 15.63GB (2040/0/0) 32772600 2 backup wu 0 - 38911 298.08GB (38912/0/0) 625121280 3 unassigned wm 2305 - 4344 15.63GB (2040/0/0) 32772600 4 unassigned wm 4345 - 6404 15.78GB (2060/0/0) 33093900 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 6385 - 6393 70.60MB (9/0/0) 144585 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) 522369540 8 boot wu 0 - 0 7.84MB (1/0/0) 16065 9 alternates wm 1 - 2 15.69MB (2/0/0) 32130 bash-3.00# zpool create test c0d0s7 bash-3.00# zpool destroy test bash-3.00# zpool create test c11d0s7 invalid vdev specification use ''-f'' to override the following errors: /dev/dsk/c11d0s7 overlaps with /dev/dsk/c11d0s2 I''d have thought that every slice overlaps s2! Ian
Ian, It looks like the error message is wrong - slice 7 overlaps slice 4 - note that slice 4 ends at c6404, but slice 7 starts at c6394. Slice 6 is also completely contained within slice 4''s range of cylinders, but that won''t matter unless you attempt to use it. Trev Ian Collins wrote:> I have to drives with the same slices and I get an odd error if I try > and create a pool on one drive, but not the other: > > Part Tag Flag Cylinders Size Blocks > 0 swap wu 3 - 264 2.01GB (262/0/0) 4209030 > 1 root wm 265 - 2304 15.63GB (2040/0/0) 32772600 > 2 backup wu 0 - 38911 298.08GB (38912/0/0) 625121280 > 3 unassigned wm 2305 - 4344 15.63GB (2040/0/0) 32772600 > 4 unassigned wm 4345 - 6404 15.78GB (2060/0/0) 33093900 > 5 unassigned wm 0 0 (0/0/0) 0 > 6 unassigned wm 6385 - 6393 70.60MB (9/0/0) 144585 > 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) 522369540 > 8 boot wu 0 - 0 7.84MB (1/0/0) 16065 > 9 alternates wm 1 - 2 15.69MB (2/0/0) 32130 > > bash-3.00# zpool create test c0d0s7 > bash-3.00# zpool destroy test > bash-3.00# zpool create test c11d0s7 > invalid vdev specification > use ''-f'' to override the following errors: > /dev/dsk/c11d0s7 overlaps with /dev/dsk/c11d0s2 > > I''d have thought that every slice overlaps s2! > > Ian > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070515/78f22768/attachment.bin>
Trevor Watson wrote:> Ian, > > It looks like the error message is wrong - slice 7 overlaps slice 4 - > note that slice 4 ends at c6404, but slice 7 starts at c6394. > > Slice 6 is also completely contained within slice 4''s range of > cylinders, but that won''t matter unless you attempt to use it. >Bugger, I didn''t spot that! I''d better fix that before I use s4 for a Live Upgrade! Cheers, Ian> Ian Collins wrote: >> I have to drives with the same slices and I get an odd error if I try >> and create a pool on one drive, but not the other: >> >> Part Tag Flag Cylinders Size Blocks >> 0 swap wu 3 - 264 2.01GB (262/0/0) >> 4209030 >> 1 root wm 265 - 2304 15.63GB (2040/0/0) >> 32772600 >> 2 backup wu 0 - 38911 298.08GB (38912/0/0) >> 625121280 >> 3 unassigned wm 2305 - 4344 15.63GB (2040/0/0) >> 32772600 >> 4 unassigned wm 4345 - 6404 15.78GB (2060/0/0) >> 33093900 >> 5 unassigned wm 0 0 >> (0/0/0) 0 >> 6 unassigned wm 6385 - 6393 70.60MB (9/0/0) >> 144585 >> 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) >> 522369540 >> 8 boot wu 0 - 0 7.84MB (1/0/0) >> 16065 >> 9 alternates wm 1 - 2 15.69MB (2/0/0) >> 32130 >> >> bash-3.00# zpool create test c0d0s7 bash-3.00# zpool destroy test >> bash-3.00# zpool create test c11d0s7 >> invalid vdev specification >> use ''-f'' to override the following errors: >> /dev/dsk/c11d0s7 overlaps with /dev/dsk/c11d0s2 >> >> I''d have thought that every slice overlaps s2! >> >> Ian >> >> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
Ian Collins wrote:> Trevor Watson wrote: > >> Ian, >> >> It looks like the error message is wrong - slice 7 overlaps slice 4 - >> note that slice 4 ends at c6404, but slice 7 starts at c6394. >> >> Slice 6 is also completely contained within slice 4''s range of >> cylinders, but that won''t matter unless you attempt to use it. >> >> > Bugger, I didn''t spot that! I''d better fix that before I use s4 for a > Live Upgrade! > >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 I get the error for any slice on this drive. Ian> Cheers, > > Ian > > >> Ian Collins wrote: >> >>> I have to drives with the same slices and I get an odd error if I try >>> and create a pool on one drive, but not the other: >>> >>> Part Tag Flag Cylinders Size Blocks >>> 0 swap wu 3 - 264 2.01GB (262/0/0) >>> 4209030 >>> 1 root wm 265 - 2304 15.63GB (2040/0/0) >>> 32772600 >>> 2 backup wu 0 - 38911 298.08GB (38912/0/0) >>> 625121280 >>> 3 unassigned wm 2305 - 4344 15.63GB (2040/0/0) >>> 32772600 >>> 4 unassigned wm 4345 - 6404 15.78GB (2060/0/0) >>> 33093900 >>> 5 unassigned wm 0 0 >>> (0/0/0) 0 >>> 6 unassigned wm 6385 - 6393 70.60MB (9/0/0) >>> 144585 >>> 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) >>> 522369540 >>> 8 boot wu 0 - 0 7.84MB (1/0/0) >>> 16065 >>> 9 alternates wm 1 - 2 15.69MB (2/0/0) >>> 32130 >>> >>> bash-3.00# zpool create test c0d0s7 bash-3.00# zpool destroy test >>> bash-3.00# zpool create test c11d0s7 >>> invalid vdev specification >>> use ''-f'' to override the following errors: >>> /dev/dsk/c11d0s7 overlaps with /dev/dsk/c11d0s2 >>> >>> I''d have thought that every slice overlaps s2! >>> >>> Ian >>> >>> >>> _______________________________________________ >>> zfs-discuss mailing list >>> zfs-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>> > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > > >
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? Trev Ian Collins wrote:> Ian Collins wrote: >> Trevor Watson wrote: >> >>> Ian, >>> >>> It looks like the error message is wrong - slice 7 overlaps slice 4 - >>> note that slice 4 ends at c6404, but slice 7 starts at c6394. >>> >>> Slice 6 is also completely contained within slice 4''s range of >>> cylinders, but that won''t matter unless you attempt to use it. >>> >>> >> Bugger, I didn''t spot that! I''d better fix that before I use s4 for a >> Live Upgrade! >> >> > 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 > > I get the error for any slice on this drive. > > Ian > >> Cheers, >> >> Ian >> >> >>> Ian Collins wrote: >>> >>>> I have to drives with the same slices and I get an odd error if I try >>>> and create a pool on one drive, but not the other: >>>> >>>> Part Tag Flag Cylinders Size Blocks >>>> 0 swap wu 3 - 264 2.01GB (262/0/0) >>>> 4209030 >>>> 1 root wm 265 - 2304 15.63GB (2040/0/0) >>>> 32772600 >>>> 2 backup wu 0 - 38911 298.08GB (38912/0/0) >>>> 625121280 >>>> 3 unassigned wm 2305 - 4344 15.63GB (2040/0/0) >>>> 32772600 >>>> 4 unassigned wm 4345 - 6404 15.78GB (2060/0/0) >>>> 33093900 >>>> 5 unassigned wm 0 0 >>>> (0/0/0) 0 >>>> 6 unassigned wm 6385 - 6393 70.60MB (9/0/0) >>>> 144585 >>>> 7 unassigned wm 6394 - 38909 249.09GB (32516/0/0) >>>> 522369540 >>>> 8 boot wu 0 - 0 7.84MB (1/0/0) >>>> 16065 >>>> 9 alternates wm 1 - 2 15.69MB (2/0/0) >>>> 32130 >>>> >>>> bash-3.00# zpool create test c0d0s7 bash-3.00# zpool destroy test >>>> bash-3.00# zpool create test c11d0s7 >>>> invalid vdev specification >>>> use ''-f'' to override the following errors: >>>> /dev/dsk/c11d0s7 overlaps with /dev/dsk/c11d0s2 >>>> >>>> I''d have thought that every slice overlaps s2! >>>> >>>> Ian >>>> >>>> >>>> _______________________________________________ >>>> zfs-discuss mailing list >>>> zfs-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>>> >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >> >> >> >-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3253 bytes Desc: S/MIME Cryptographic Signature URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070515/038ee452/attachment.bin>
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) 522369540If 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