cancel
Showing results for 
Search instead for 
Did you mean: 

Imported diskgroup name is different from the private region

pakpak
Level 2

Hello All,

 

I seem to be confused...  I have a diskgroup currently imported as externaldb-db2bkup15dg.

tagmastore-usp0_19 auto:cdsdisk   db2bkup15-01  externaldb-db2bkup15dg online nohotuse      c5t60060E8016016F000001016F0000015Dd0s2 -

 

When I look at the private region, I see that it is different.

bash-3.00# vxdisk -v list c5t60060E8016016F000001016F0000015Dd0s2 |grep group
group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
 
 
When I look at the diskgroup on another server, it's telling  externaldb-db2ins15dg instead of externaldb-db2bkup15dg.  I'm assuming its grabbing that information from the private region.
 
bash-3.00# vxdisk -e -o alldgs list |grep -i db2ins15
tagmastore-usp0_22 auto:cdsdisk   -            (externaldb-db2ins15dg) online               c5t60060E8016016F000001016F0000015Dd0s2 -
 
 
Will this cause issues if I were to deport/import the diskgroup to another server?   I'm running 5.1 btw.
 
 
 

 

 
1 ACCEPTED SOLUTION

Accepted Solutions

g_lee
Level 6

Is this particular diskgroup under cluster control, or was it imported manually?

If it was a manual import - is it possible it was imported with a temporary new name (the fact the noautoimport flag is set in vxdisk list output makes me suspect this could be possible).

ie: # vxdg -t -n {tempname} import {dg}

this would explain why the host with the dg imported shows a different name, but the private region is not updated.

from vxdg man page:

https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/manualpages/html/manpages/volume_mana...

Import fails if the specified disk group name is either a reserved name (such as bootdg or nodg) or an existing disk group name. The disk group can be renamed on import using -n newname. If -n is used with the -t option, the stored name of the disk group remains unchanged, but the importing host knows the disk group under the new name; otherwise, the name change is permanent.

example/test:

host1 # vxdisksetup -i pp_emc_clariion0_2
host1 # vxdg init testdg testdg01=pp_emc_clariion0_2
host1 # vxprint -qhtrg testdg
dg testdg       default      default  31000    1386050307.171.host1
 
dm testdg01     pp_emc_clariion0_2 auto 65536  20904448 -
host1 # vxdg list testdg
Group:     testdg
dgid:      1386050307.171.host1
import-id: 1024.170
flags:     cds
version:   140
alignment: 8192 (bytes)
ssb:            on
autotagging:    on
detach-policy: global
dg-fail-policy: dgdisable
copies:    nconfig=default nlog=default
config:    seqno=0.1027 permlen=48144 free=48141 templen=2 loglen=7296
config disk pp_emc_clariion0_2 copy 1 len=48144 state=clean online
log disk pp_emc_clariion0_2 copy 1 len=7296
host1 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name=testdg01 id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050308 seqno=0.7
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower82c     state=enabled
host1 # vxdg deport testdg
host1 # vxdisk -o alldgs list |grep test
pp_emc_clariion0_2 auto:cdsdisk    -            (testdg)     online
host1 # vxdg -t -n newnamedg import testdg
host1 # vxdg list
NAME         STATE           ID
[...]
newnamedg    enabled,cds          1386050307.171.host1
host1 # vxdisk -o alldgs list |egrep "test|new"
pp_emc_clariion0_2 auto:cdsdisk    testdg01     newnamedg    online
host1 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name=testdg01 id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig noautoimport imported
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050541 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower82c     state=enabled
host1 # vxprint -qhtrg newnamedg
dg newnamedg    default      default  31000    1386050307.171.host1
 
dm testdg01     pp_emc_clariion0_2 auto 65536  20904448 -
host1 #
 
meanwhile on host2, it still sees the testdg name as the name change is temporary due to the combination of -t & -n flags on import:
host2 # vxdisk -o alldgs list |egrep "test|new"
pp_emc_clariion0_2 auto:cdsdisk    -            (testdg)     online
host2 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name= id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig noautoimport
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050541 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower46c     state=enabled
 

View solution in original post

6 REPLIES 6

Gaurav_S
Moderator
Moderator
   VIP    Certified

Hello..

Need some more information ..

1. Is this is a clustered setup ?

2. Are you using snapshots with diskgroup split & join ?

3. Can you also let us know when was last update happened to diskgroup config ? you can find this information from /etc/vx/cbr/bk directory ...

4. also paste a full "vxdisk list <disk>" output from both the servers ?

 

G

pakpak
Level 2

Thank you for responding!

 

1. Is this is a clustered setup ?  Yes.

2. Are you using snapshots with diskgroup split & join ?  No.

3. Can you also let us know when was last update happened to diskgroup config ? you can find this information from /etc/vx/cbr/bk directory ...  Nov. 1st 2012.

4. also paste a full "vxdisk list <disk>" output from both the servers ?

bash-3.00# vxdisk list c5t60060E8016016F000001016F0000015Dd0s2
Device:    tagmastore-usp0_22
devicetag: tagmastore-usp0_22
type:      auto
hostid:    externaldb-n3
disk:      name= id=1351725217.150.externaldb-n3
group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig noautoimport
pubpaths:  block=/dev/vx/dmp/tagmastore-usp0_22s2 char=/dev/vx/rdmp/tagmastore-usp0_22s2
guid:      -
udid:      HITACHI%5FOPEN-V%20%20%20%20%20%20-SUN%5F1016F%5F015D
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20905648 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1351726193 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
c5t60060E8016016F000001016F0000015Dd0s2 state=enabled
 

 

bash-3.00# vxdisk list c5t60060E8016016F000001016F0000015Dd0s2
Device:    tagmastore-usp0_19
devicetag: tagmastore-usp0_19
type:      auto
hostid:    externaldb-n3
disk:      name=db2bkup15-01 id=1351725217.150.externaldb-n3
group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig nohotuse noautoimport imported
pubpaths:  block=/dev/vx/dmp/tagmastore-usp0_19s2 char=/dev/vx/rdmp/tagmastore-usp0_19s2
guid:      {9975df22-23b0-11e2-9edf-001b21c58a11}
udid:      HITACHI%5FOPEN-V%20%20%20%20%20%20-SUN%5F1016F%5F015D
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20905648 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1351726193 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
c5t60060E8016016F000001016F0000015Dd0s2 state=enabled
 

 

 

Gaurav_S
Moderator
Moderator
   VIP    Certified

Both above outputs currently are showing same diskgroup name & I believe these outputs are from different servers ?

group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3

group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3

 

So currently only which output is showing the DG name incorrect ? isit a full "vxdisk list" ?

Please paste from both the servers (also please put host name in the shell so that can identify two different servers)

# vxdisk list

# vxdisk -e list

# vxdg list

# vxdg list externaldb-db2ins15dg

# vxdg list externaldb-db2bkup15dg

 

G

 

pakpak
Level 2

Both above outputs currently are showing same diskgroup name & I believe these outputs are from different servers ?  Correct.

So currently only which output is showing the DG name incorrect ? isit a full "vxdisk list" ?  They are both showing externaldb-db2ins15dg, however it is currently imported on one of the nodes as externaldb-db2bkup15dg which is correct.

 

Here it shows me that drive c5t60060E8016016F000001016F0000015Dd0s2 is associated with externaldb-db2bkup15dg.

externaldb-n3# vxdisk -e -o alldgs list |grep -i externaldb-db2bkup15
tagmastore-usp0_19 auto:cdsdisk   db2bkup15-01  externaldb-db2bkup15dg online nohotuse      c5t60060E8016016F000001016F0000015Dd0s2 -
 
 
However, when I run a vxdisk list on the drive, it's telling me it belongs to externaldb-db2ins15dg.
 
externaldb-n3# vxdisk -v list c5t60060E8016016F000001016F0000015Dd0s2
Device:    tagmastore-usp0_19
devicetag: tagmastore-usp0_19
type:      auto
hostid:    externaldb-n3
disk:      name=db2bkup15-01 id=1351725217.150.externaldb-n3
group:     name=externaldb-db2ins15dg id=1351725730.154.externaldb-n3
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig nohotuse noautoimport imported
pubpaths:  block=/dev/vx/dmp/tagmastore-usp0_19s2 char=/dev/vx/rdmp/tagmastore-usp0_19s2
guid:      {9975df22-23b0-11e2-9edf-001b21c58a11}
udid:      HITACHI%5FOPEN-V%20%20%20%20%20%20-SUN%5F1016F%5F015D
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20905648 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1351726193 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Annotations:
 tag      udid_asl=HITACHI%5FOPEN-V%20%20%20%20%20%20-SUN%5F1016F%5F015D
Multipathing information:
numpaths:   1
c5t60060E8016016F000001016F0000015Dd0s2 state=enabled
 
Even though it's imported as externaldb-db2bkup15dg,  why is it when I run a vxdisklist on the drive, it is telling me different?   
 

 

 

 

 

g_lee
Level 6

Is this particular diskgroup under cluster control, or was it imported manually?

If it was a manual import - is it possible it was imported with a temporary new name (the fact the noautoimport flag is set in vxdisk list output makes me suspect this could be possible).

ie: # vxdg -t -n {tempname} import {dg}

this would explain why the host with the dg imported shows a different name, but the private region is not updated.

from vxdg man page:

https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/manualpages/html/manpages/volume_mana...

Import fails if the specified disk group name is either a reserved name (such as bootdg or nodg) or an existing disk group name. The disk group can be renamed on import using -n newname. If -n is used with the -t option, the stored name of the disk group remains unchanged, but the importing host knows the disk group under the new name; otherwise, the name change is permanent.

example/test:

host1 # vxdisksetup -i pp_emc_clariion0_2
host1 # vxdg init testdg testdg01=pp_emc_clariion0_2
host1 # vxprint -qhtrg testdg
dg testdg       default      default  31000    1386050307.171.host1
 
dm testdg01     pp_emc_clariion0_2 auto 65536  20904448 -
host1 # vxdg list testdg
Group:     testdg
dgid:      1386050307.171.host1
import-id: 1024.170
flags:     cds
version:   140
alignment: 8192 (bytes)
ssb:            on
autotagging:    on
detach-policy: global
dg-fail-policy: dgdisable
copies:    nconfig=default nlog=default
config:    seqno=0.1027 permlen=48144 free=48141 templen=2 loglen=7296
config disk pp_emc_clariion0_2 copy 1 len=48144 state=clean online
log disk pp_emc_clariion0_2 copy 1 len=7296
host1 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name=testdg01 id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050308 seqno=0.7
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower82c     state=enabled
host1 # vxdg deport testdg
host1 # vxdisk -o alldgs list |grep test
pp_emc_clariion0_2 auto:cdsdisk    -            (testdg)     online
host1 # vxdg -t -n newnamedg import testdg
host1 # vxdg list
NAME         STATE           ID
[...]
newnamedg    enabled,cds          1386050307.171.host1
host1 # vxdisk -o alldgs list |egrep "test|new"
pp_emc_clariion0_2 auto:cdsdisk    testdg01     newnamedg    online
host1 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name=testdg01 id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig noautoimport imported
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050541 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower82c     state=enabled
host1 # vxprint -qhtrg newnamedg
dg newnamedg    default      default  31000    1386050307.171.host1
 
dm testdg01     pp_emc_clariion0_2 auto 65536  20904448 -
host1 #
 
meanwhile on host2, it still sees the testdg name as the name change is temporary due to the combination of -t & -n flags on import:
host2 # vxdisk -o alldgs list |egrep "test|new"
pp_emc_clariion0_2 auto:cdsdisk    -            (testdg)     online
host2 # vxdisk list pp_emc_clariion0_2
Device:    pp_emc_clariion0_2
devicetag: pp_emc_clariion0_2
type:      auto
hostid:    host1
disk:      name= id=1386050274.169.host1
group:     name=testdg id=1386050307.171.host1
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig noautoimport
pubpaths:  block=/dev/vx/dmp/pp_emc_clariion0_2s2 char=/dev/vx/rdmp/pp_emc_clariion0_2s2
guid:      {d9c74404-1dd1-11b2-bdab-00144f4ca2b5}
udid:      DGC%5FVRAID%5FAPM00121302226%5F600601600300270048CCBC411EE6E111
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=20904448 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1386050541 seqno=0.11
ssb:       actual_seqno=0.0
headers:   0 240
configs:   count=1 len=48144
logs:      count=1 len=7296
Defined regions:
 config   priv 000048-000239[000192]: copy=01 offset=000000 enabled
 config   priv 000256-048207[047952]: copy=01 offset=000192 enabled
 log      priv 048208-055503[007296]: copy=01 offset=000000 enabled
 lockrgn  priv 055504-055647[000144]: part=00 offset=000000
Multipathing information:
numpaths:   1
emcpower46c     state=enabled
 

pakpak
Level 2

Looks like you got it!  Thanks, appreciate the help!