SVM sees non-unique device IDs

Johnathan Thibodeau jthibo at chebucto.ns.ca
Wed Mar 18 13:22:09 EST 2009


Hello,

I am having a problem setting up a meta device using SVM on Solaris 9.

While trying to create a couple single slice concatenations, each using a 
different (but model-identical) disk, the metainit command claims that the 
second concatenation overlaps with the first. Eg:

# metainit d3 1 1 c1t3d0s0
d3: Concat/Stripe is setup

# metainit d4 1 1 c2t4d0s0
metainit: halifax: c2t4d0s0: overlaps with device in d3

The metastat command shows the first concat was created, but the device ID 
for the disk is not right.

# metastat
d3: Concat/Stripe
     Size: 143246394 blocks (68 GB)
     Stripe 0:
         Device     Start Block  Dbase   Reloc
         c1t3d0s0          0     No      Yes
...
Device Relocation Information:
Device   Reloc  Device ID
c1t3d0   Yes    id1,sd at w5000000000000000

If I reverse the order of the metainit commands, the d4 concat is created 
with the c2t4d0 disk, however the device ID shown by metastat is identical 
to that shown for the c1t3d0 disk.

I have tried running 'metadevadm -u' on the disks, but that changed 
nothing.

The disks used here are Seagate model ST373455LC. They are housed in 
external Sun enclosures. There are two other disks, mounted internally, 
already in use by SVM which are identified correctly:

c0t1d0   Yes    id1,sd at SSEAGATE_ST373307LC______3HZ06B450000732282SN
c0t0d0   Yes    id1,sd at SSEAGATE_ST373307LC______3HZ04E8Q00007320FHV4

I'm wondering where I should look for how the SVM commands determine the 
device ID, or if maybe there's a way to set or force the ID.

Thanks,

Johnathan


More information about the sunmanagers mailing list