Cannot mirror rootdg

[crich]

OS - Solaris10 

Veritas SF - 6.0

I cannot remirror my rootdg after disassociating the plexes when applying the latest OS patch bundle to the server.  I was able to run vxdisk and vxdg and get the disk added to the dg but when I tried to mirror using vxdiskadm it fails with the following.

VxVM vxmirror INFO V-5-2-22   Mirror volume rootvol ...
  VxVM  ERROR V-5-2-673 Mirroring of disk rootdisk failed.
  Error:
  VxVM vxdisksetup ERROR V-5-2-43 c0t1d0: Invalid disk device for vxdisksetup
VxVM vxdg ERROR V-5-1-10127 associating disk-media mirrordisk with c0t1d0s2:
        Disk private region contents are invalid
! vxassist -g rootdg mirror rootvol mirrordisk
VxVM vxassist ERROR V-5-1-325 dm:mirrordisk: No disks match specification
! vxbootsetup -g rootdg
VxVM vxmirror NOTICE V-5-2-3631 The following volumes were not mirrored:
   rootvol var swapvol usr opt

vxdisk output

DEVICE       TYPE            DISK         GROUP        STATUS
c0t0d0s2     auto:sliced     rootdisk     rootdg       online
c0t1d0s2     auto:cdsdisk    mirrordisk   rootdg       online

vxdisk list <disk>output

Device:    c0t1d0s2
devicetag: c0t1d0
type:      auto
hostid:    fjus176
disk:      name=mirrordisk id=1352897141.147.fjus176
group:     name=rootdg id=1331901259.14.fjus176
info:      format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/c0t1d0s2 char=/dev/vx/rdmp/c0t1d0s2
guid:      {32edebec-2e59-11e2-a0ae-00144f03428c}
udid:      SEAGATE%5FST914603SSUN146G%5FDISKS%5F303934363832314157540000
site:      -
version:   3.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=2 offset=65792 len=286632832 disk_offset=0
private:   slice=2 offset=256 len=65536 disk_offset=0
update:    time=1352897151 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
c0t1d0s2        state=enabled
 

[mikebounds]

The 2 disks may be formatted differently - can you provide vxdisk list detailed output for the first disk (i.e vxdisk list c0t0d0s2)

Mike

[crich]

Here you go.

Device:    c0t0d0s2
devicetag: c0t0d0
type:      auto
hostid:    fjus176
disk:      name=rootdisk id=1331901257.12.fjus176
group:     name=rootdg id=1331901259.14.fjus176
info:      format=sliced,privoffset=1,pubslice=7,privslice=4
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/c0t0d0s7 char=/dev/vx/rdmp/c0t0d0s7
privpaths: block=/dev/vx/dmp/c0t0d0s4 char=/dev/vx/rdmp/c0t0d0s4
guid:      -
udid:      SEAGATE%5FST914603SSUN146G%5FDISKS%5F303934363832314456340000
site:      -
version:   2.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=7 offset=1 len=286617216 disk_offset=0
private:   slice=4 offset=1 len=81407 disk_offset=286617216
update:    time=1352899407 seqno=0.26
ssb:       actual_seqno=0.0
headers:   0 248
configs:   count=1 len=60061
logs:      count=1 len=9100
Defined regions:
 config   priv 000017-000247[000231]: copy=01 offset=000000 enabled
 config   priv 000249-060078[059830]: copy=01 offset=000231 enabled
 log      priv 060079-069178[009100]: copy=01 offset=000000 enabled
Multipathing information:
numpaths:   1
c0t0d0s2        state=enabled
 

[mikebounds]

c0t0d0s2 has format "sliced" and c0t1d0s2 has cds format, so I would make c0t1d0s2 sliced with the same offsets using vxdisksetup to reinitialise disk (you will need to remove from rootdg first).

Mike

[crich · Accepted solution]

Actually found out that Symantec has a bulletin out on this issue.  Our team is downloading the patcha nd will install it soon..  I will post on here how things work out.  The cdsdisk formatting is the issue.  This bug is for 5.1 and 6.0 when used with Generic_147440-20 and later.  Thanks to everyone for your help.