The deviceid on the disk appears suspicious. The numbers 202020 are the ascii. So I would expect a target address to be more like c4t<port_number>__XIV1030___1019________3
What disks are these ? Is there a firmware upgrade ? Also could you try with S10U1 since that is now available. -Sanjay Tony Nguyen wrote: > Hi Leon, > > Sorry for a late response but it was the holiday break here in the US > and we just got back today. I did a quick search but couldn't find > anything related to what you're seeing. I have some comments and > questions inline to help us figure out this issue. > > I'm also cc'ing the lvm-discuss alias in hope that other SVM engineers > can give us additional insight. > > -tony > >> Hi Tony, >> I found your e-mail in OpenSolaris LVM forum. >> I have a quextion related to Solaris 10 SVM - could you please help me. >> I didn't check this in Solaris Express and didn't send the bug report >> to Sun Support that's why I need your advice. >> The problem is: I cannot add a device to the metaset in S10/x86 01/06. >> Here is my scenario: >> # metadb -a -f c0d0s3 c0d0s4 c0d0s5 >> # metadb >> flags first blk block count >> a m pc luo 16 8192 /dev/dsk/c0d0s3 >> a pc luo 16 8192 /dev/dsk/c0d0s4 >> a pc luo 16 8192 /dev/dsk/c0d0s5 >> # metaset -s test -a >> /dev/rdsk/c4t5849562D494E4320584956313033302020202020313031393020202020202 >> >> 033d0 >> # metaset -s test >> >> Set name = test, Set number = 1 >> >> Host Owner >> chuk Yes >> >> Drive >> Dbase >> >> /dev/dsk/c4t5849562D494E43205849563130333020202020203130313930202020202020 >> >> 33d0 Yes >> >> # metaset -s test -a >> /dev/rdsk/c4t5849562D494E4320584956313033302020202020313031393020202020202 >> >> 034d0 >> metaset: chuk: /: No such file or directory >> >> both dd # metadb >> flags first blk block count >> a m pc luo 16 8192 /dev/dsk/c0d0s3 >> a pc luo 16 8192 /dev/dsk/c0d0s4 >> a pc luo 16 8192 /dev/dsk/c0d0s5 >> # metaset -s test -a >> /dev/rdsk/c4t5849562D494E4320584956313033302020202020313031393020202020202 >> >> 033d0 >> # metaset -s test >> >> Set name = test, Set number = 1 >> >> Host Owner >> chuk Yes >> >> Drive >> Dbase >> >> Both >> /dev/dsk/c4t5849562D494E43205849563130333020202020203130313930202020202020 >> >> 33d0 and >> /dev/rdsk/c4t5849562D494E4320584956313033302020202020313031393020202020202 >> >> 033d0 are 1.5TB mpxio disks with EFI label and slice 0 starting from >> block 34, occupyimng the whole disk. >> >> What am I doing wrong? Is it a bug? Or the metasets are not supported >> in non-SunCluster environment. >> >> > Metasets or sets are supported in non-SunCluster environment. In fact, > we recommend metasets to help ease management of metadevices, except > metadevices that are used for root mirroring. > > Let me do a quick recap to make sure that I understand the problem here. > > The machine is running stock S10 01/06 (S10 Update 1) with mpxio. > You can add one of the mpxio disks (the disk ended with 33d0) but not > the other one. > > Is there any differences between these mpxio disks (e.g. disk size, > storage unit model)? > Can you add the regular drives (non-multipath drives) to the set? > >> I had the similar problem with S10/x86 03/05 with SunCluster installed. >> Then I installed S10 01/06 and decided to check things before I >> install the Sun Cluster. >> >> > > Can you provide the explorer output so I can see the system's > configuration info? The explorer's script is at > > http://classic.sunsolve.sun.com/pub-cgi/show.pl?target=explorer/explorer > >> Your opinion will be appreciated. I need to build NFS HA cluster based >> on multi-tera volumes using SVM so I need to know is there any >> showstopper. >> >> >> > Cool. > > > _______________________________________________ > lvm-discuss mailing list > lvm-discuss at opensolaris.org
