Unable to evacuate, mirror, or replace disks with VERITAS Volume Manager (tm) 3.2 or 3.5 if disks have been initialized under Volume Manager 3.1.

Article:TECH91525  |  Created: 2003-01-04  |  Updated: 2004-01-22  |  Article URL http://www.symantec.com/docs/TECH91525
Article Type
Technical Solution

Product(s)

Environment

Issue



Unable to evacuate, mirror, or replace disks with VERITAS Volume Manager (tm) 3.2 or 3.5 if disks have been initialized under Volume Manager 3.1.

Solution



Note: In Volume Manager 3.2, major changes have been made to the default disk layout.

For Volume Manager 3.2, the layout looks like this:

1. One cylinder is used for private region

2. One unused cylinder

3. The remainder of the disk is used for the public region.


For Volume Manager 3.5, the layout looks like this:

1. One unused cylinder.

2. Two cylinders used for private region.

3. The remainder of the disk is used for public region.


The following two disks are of the same size and have the following information:

# diskinfo /dev/rdsk/c0t4d0
SCSI describe of /dev/rdsk/c0t4d0:
            vendor: SEAGATE
        product id: ST15150W
              type: direct access
              size: 4194157 Kbytes
  bytes per sector: 512


# diskinfo /dev/rdsk/c0t6d0
SCSI describe of /dev/rdsk/c0t6d0:
            vendor: SEAGATE
        product id: ST15150W
              type: direct access
              size: 4194157 Kbytes
  bytes per sector: 512

Disk c0t4d0 was initialized with Volume Manager 3.1.

From the vxdisk list output utility:

# vxdisk list c0t4d0
Device:    c0t4d0
devicetag: c0t4d0
type:      simple
hostid:    yang
disk:      name=testdg01 id=1054661317.1079.yang
group:     name=testdg id=1054661331.1082.yang
info:      privoffset=128
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/c0t4d0 char=/dev/vx/rdmp/c0t4d0
version:   2.1
iosize:    min=1024 (bytes) max=64 (blocks)
public:    slice=0 offset=1152 len=4193005
private:   slice=0 offset=128 len=1024
update:    time=1054661332 seqno=0.5
headers:   0 248
configs:   count=1 len=727
logs:      count=1 len=110
Defined regions:
config   priv 000017-000247[000231]: copy=01 offset=000000 enabled
config   priv 000249-000744[000496]: copy=01 offset=000231 enabled
log      priv 000745-000854[000110]: copy=01 offset=000000 enabled
lockrgn  priv 000855-000919[000065]: part=00 offset=000000
Multipathing information:
numpaths:   1
c0t4d0  state=enabled

When data needs to be moved from disk c0t4d0, which was initialized with Volume Manager 3.1, to disk c0t6d0, which was initialized with Volume Manager 3.2 or Volume Manager (without update 1 patches), the publen and puboffset have to be the same. The publen and puboffset can be adjusted using the following commands:

#/etc/vx/bin/vxdisksetup -i c0t6d0 publen=4193005 puboffset=1152 privlen=1024 privoffset=128

# vxdisk list c0t6d0
Device:    c0t6d0
devicetag: c0t6d0
type:      simple
hostid:
disk:      name= id=1054663953.1057.yang
group:     name= id=
info:      privoffset=128
flags:     online ready private autoconfig autoimport
pubpaths:  block=/dev/vx/dmp/c0t6d0 char=/dev/vx/rdmp/c0t6d0
version:   2.2
iosize:    min=1024 (bytes) max=64 (blocks)
public:    slice=0 offset=1152 len=4191264
private:   slice=0 offset=128 len=1024
update:    time=1054663954 seqno=0.1
headers:   0 248
configs:   count=1 len=727
logs:      count=1 len=110
Defined regions:
config   priv 000017-000247[000231]: copy=01 offset=000000 disabled
config   priv 000249-000744[000496]: copy=01 offset=000231 disabled
log      priv 000745-000854[000110]: copy=01 offset=000000 disabled
lockrgn  priv 000855-000919[000065]: part=00 offset=000000
Multipathing information:
numpaths:   1
c0t6d0  state=enabled

Note: Publen is different, and thus, disk evac utility would fail. The error message is given below.

# /usr/lib/vxvm/bin/vxevac -g testdg testdg01 testdg02
vxvm:vxassist: ERROR: Cannot allocate space to replace subdisks
vxevac: Aborting disk evacuation


Solution:

This has been addressed to incident 109750 and has been fixed by Volume Manager 3.2 patch 02 and Volume Manager 3.5 update 1 patches.

1. For Volume Manager 3.2:

Install Volume Manager 3.2 patch 02, PHCO_28378 and PHKL_28379.

The patches listed above, or their superseding patches, can be obtained through the Hewlett-Packard (HP) IT Resource Center Web site:  http://ITresourcecenter.hp.com
Select Individual Patches to search the patch database.


For Volume Manager 3.5:

Install Volume Manager 3.5 update 2 patches.

Refer to TechNote 260954 for details. For more information about this TechNote, see the Related Documents section.

2. Reinitialize the disk:

# vxdisk -f init c0t6d0 publen=4193005

3. Add the disk to the disk group:

# vxdg -g testdg adddisk testdg02=c0t6d0

4. Evacuate the disk again:

# /usr/lib/vxvm/bin/vxevac -g testdg testdg01 testdg02

Supplemental Materials

SourceiTools
Value109750
DescriptionReplacement disk may have a different publen


Legacy ID



258911


Article URL http://www.symantec.com/docs/TECH91525


Terms of use for this information are found in Legal Notices