cancel
Showing results for 
Search instead for 
Did you mean: 

VxVM 5.0 - disk name uniqueness

mlukes
Level 3
Dear experts,

I have question regarding disk name (also known as disk media name) uniqueness in VxVM 5.0. I would like decided to use naming scheme described below in extended distance cluster environment:

<SITE ID>disk<SEQUENCE NUMER>

where <SITE ID> identifies a site (data center) in extended distance cluster and <SEQUENCE NUMBER> is unique number inside the current disk group (its format is ###). Below is example of my configuration:

dc1srv1:/root > vxdisk list
c3t0d2 auto:none  dc2disk001  dg01  online shared
c3t0d3 auto:none  dc2disk002  dg01  online shared
c3t0d4 auto:none  dc2disk003  dg01  online shared
c3t0d5 auto:none  dc2disk001  dg02  online shared
...
c5t0d2 auto:none dc1disk001 dg01 online shared
c5t0d3 auto:none dc1disk002 dg01 online shared
c5t0d4 auto:none dc1disk003 dg01 online shared
c5t0d5 auto:none dc1disk001 dg02 online shared
...

I have used this naming scheme previously, in fact not in extended distance cluster environment. Now everything seemed to be OK, but now when I used command vxdisk list <device> I received the ERROR message:

VxVM vxdisk ERROR V-5-1-0 <device> - Record in multiple disk groups

Below is concrete example:

dc1srv1:/root > vxdisk list c3t0d2
Device: c3t0d2
devicetag: c3t0d2
type: auto
clusterid: cluster1
disk: name=dc2disk001 id=1244618120.47.dc1srv1
VxVM vxdisk ERROR V-5-1-0 dc2disk001 - Record in multiple disk groups
group: name=dg01 id=1244618683.57.dc1srv1
info: format=cdsdisk,privoffset=128
flags: online ready private autoconfig shared autoimport imported
pubpaths: block=/dev/vx/dmp/c3t0d2 char=/dev/vx/rdmp/c3t0d2
guid: {75324838-1dd2-11b2-8c16-00237da92ec8}
udid: HP%5F50%5F13131%5F50%201313100DC
site: dc2
version: 3.1
iosize: min=512 (bytes) max=256 (blocks)
public: slice=0 offset=32896 len=8345984 disk_offset=0
private: slice=0 offset=128 len=32768 disk_offset=0
update: time=1244622704 seqno=0.9
ssb: actual_seqno=0.0
headers: 0 120
configs: count=1 len=24072
logs: count=1 len=3648
Defined regions:
config priv 000024-000119[000096]: copy=01 offset=000000 enabled
config priv 000128-024103[023976]: copy=01 offset=000096 enabled
log priv 024104-027751[003648]: copy=01 offset=000000 disabled
lockrgn priv 027752-027823[000072]: part=00 offset=000000
Multipathing information:
numpaths: 2
c3t0d2 state=enabled
c7t0d2 state=enabled

Does it mean that disk name must be unique in the whole system not just inside the current disk group?

The description in the manual for VxVM 5.0 is not clear to me. In an older manual I found a note that disk name has to be unique inside the current disk group but this note is not in the manual for VxVM 5.0. By default VxVM 5.0 uses naming scheme <DG NAME><SEQUENCE ID> it guarantees that disk name is unique in the whole system.

Thanks and best regards,
Marek Lukes

2 REPLIES 2

Ed_Cook
Level 3
Employee Certified
Marek,


You should be able to use the same dm name inside different diskgroups in a standalone configuration. To get a better idea what type of cluster you have configured could you please post the output from gabconfig -a.  I am thinking this problem could be related to cluster.

Thanks,

ED

mlukes
Level 3
Hi Ed,

thanks for your replay. Below is output of gabconfig -a you requested. In fact there are 4 nodes in Serviceguard cluster (HPUX 11.31) but one is currently down.
dc1srv1:/root > gabconfig -a
GAB Port Memberships
===============================================================
Port a gen 1c3af04 membership ;123
Port b gen 1c3af05 membership ;123
Port d gen 1c3af08 membership ;123
Port f gen 1c3af0c membership ;123
Port v gen 1c3af07 membership ;123
Port w gen 1c3af0a membership ;123


Best regards,
Marek