Discussion:
[Veritas-vx] vxvm failed to import 2T vm disk
Carl E. Ma
2011-01-21 22:21:35 UTC
Permalink
Hello,

We are running Veritas Volume Manager 5.1SP1 on solaris 10 and experiencing problem to import one 4TByte disk group, which has two concatenated 2T disks.

The alerts(on our Veritas Operations Manager console when rebooting server) are "disk asm_25000_33 import failed". After server up, I can import disk group WITHOUT problem. It just failed to import disks when server reboot. I am not sure whether the problem is related to disk size or active-active array path.

I initialized both disks as EFI disk with sliced format.

bash-3.00# vxdisk list | grep ams_25000
ams_25000_32 auto:sliced - - online
ams_25000_33 auto:sliced - - online

Both SAN disks have two active paths.

bash-3.00# vxdisk list ams_25000_32
Device: ams_25000_32
devicetag: ams_25000_32
type: auto
hostid:
disk: name= id=1295645183.33.sbtorsvr158
group: name= id=
info: format=sliced,privoffset=1,pubslice=4,privslice=3
flags: online ready private autoconfig autoimport
pubpaths: block=/dev/vx/dmp/ams_25000_32s4 char=/dev/vx/rdmp/ams_25000_32s4
privpaths: block=/dev/vx/dmp/ams_25000_32s3 char=/dev/vx/rdmp/ams_25000_32s3
guid: -
udid: HITACHI%5FDF600F%5F87040535%5F0020
site: -
version: 2.1
iosize: min=512 (bytes) max=256 (blocks)
public: slice=4 offset=0 len=4494467005 disk_offset=65570
private: slice=3 offset=1 len=65535 disk_offset=34
update: time=1295646005 seqno=0.9
ssb: actual_seqno=0.0
headers: 0 248
configs: count=1 len=48345
logs: count=1 len=7325
Defined regions:
config priv 000017-000247[000231]: copy=01 offset=000000 enabled
config priv 000249-048362[048114]: copy=01 offset=000231 enabled
log priv 048363-055687[007325]: copy=01 offset=000000 enabled
Multipathing information:
numpaths: 2
c5t84d0 state=enabled
c4t84d0 state=enabled

Thanks in advance,

carl

Loading...