cancel
Showing results for 
Search instead for 
Did you mean: 

vxmirror giving error

sam321
Level 4

root@CLFPAP06 # vxprint -htg rootdg

dg rootdg       default      default  113000   1224692943.6.GSMPAP07

dm rootdg01     c0t0d0s2     auto     81407    143267904 -
dm rootdg02     c0t1d0s2     auto     81407    143267904 -

v  rootvol      -            ENABLED  ACTIVE   41945472 ROUND     -        root
pl rootvol-01   rootvol      ENABLED  ACTIVE   41945472 CONCAT    -        RW
sd rootdg01-02  rootvol-01   rootdg01 20972735 41945472 0         c0t0d0   ENA

v  u01vol       -            ENABLED  ACTIVE   12582912 SELECT    -        fsgen
pl u01vol-01    u01vol       ENABLED  ACTIVE   12582912 CONCAT    -        RW
sd rootdg01-06  u01vol-01    rootdg01 125846591 12582912 0        c0t0d0   ENA

v  u13vol       -            ENABLED  ACTIVE   25165824 SELECT    -        fsgen
pl u13vol-02    u13vol       ENABLED  ACTIVE   25175424 CONCAT    -        RW
sd rootdg01-01  u13vol-02    rootdg01 10175    20962560 0         c0t0d0   ENA
sd rootdg01-03  u13vol-02    rootdg01 119557823 4212864 20962560  c0t0d0   ENA

v  u14vol       -            ENABLED  ACTIVE   10485760 SELECT    -        fsgen
pl u14vol-01    u14vol       ENABLED  ACTIVE   10485760 CONCAT    -        RW
sd rootdg01-04  u14vol-01    rootdg01 73409663 10485760 0         c0t0d0   ENA

v  u16vol       -            ENABLED  ACTIVE   25165824 SELECT    -        fsgen
pl u16vol-01    u16vol       ENABLED  ACTIVE   25175424 CONCAT    -        RW
sd rootdg01-05  u16vol-01    rootdg01 94382399 25175424 0         c0t0d0   ENA

want to mirror rootdg
command used:

vxmirror -g rootdg rootdg01 rootdg02 &

error getting:

root@CLFPAP06 # ! vxassist -g rootdg mirror rootvol rootdg02
VxVM vxprint ERROR V-5-1-924 Record swapvol1 not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
/usr/lib/vxvm/bin/vxbootsetup: test: unknown operator c0t0d0
VxVM vxassist ERROR V-5-1-510 Could not setup boot partition for new root mirror
! vxbootsetup -g rootdg
VxVM vxprint ERROR V-5-1-924 Record swapvol1 not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
VxVM vxprint ERROR V-5-1-924 Record - not found
/usr/lib/vxvm/bin/vxbootsetup: test: unknown operator c0t0d0
VxVM vxmirror NOTICE V-5-2-3631 The following volumes were not mirrored:
   rootvol u14vol u16vol u01vol

[1]+  Exit 1                  vxmirror -g rootdg rootdg01 rootdg02


os:solaris 10

1 ACCEPTED SOLUTION

Accepted Solutions

Gaurav_S
Moderator
Moderator
   VIP    Certified

ok, public & private region looks similar in both the disks...

Can your vxprint see a swapvol now ?  & are you getting the same error after issuing the same command ?

I would recommend to run vxmirror -g rootdg  (not vxassist mirror)..

If the above mirror fails, I see one more issue:

Notice the disk_offset values of two disks:

public:    slice=3 offset=1 len=143267904 disk_offset=0
private:   slice=4 offset=1 len=81407 disk_offset=143267904 <<<<<<<<<<<<<

public:    slice=3 offset=0 len=143267904 disk_offset=81408
private:   slice=4 offset=1 len=81407 disk_offset=0

though public & private region lengths are same however disk offset is different, it would be good  if you keep them same... this would be little tricky to initialize disk like this because you don't have any switch called  "disk_offset" to define in "vxdisksetup" command .. If you want to make these parameters similar, you have to do following:

-- Make sure which disk server is booted (prtconf -pv
 grep -i bootpath) lets assume it booted from rootdisk i.e c0t0d0

-- you can remove all the mirrors from rootmirror disk (use vxplex dis)

-- take rootmirror disk out of veritas (vxdg -g rootdg rmdisk) -- make sure you have deleted all the components from rootmirror disk. Take extra precaution before deleting, make sure there is no volume which is mounted from rootmirror disk

-- Reinitialize rootmirror again with following options:

# vxdisksetup -i c0t1d0  privlen=81407  privoffset=143267904  publen=143267904  puboffset=0  format=sliced pubslice=4 privslice=3

above command should make disk struncture of root mirror similar to rootdisk.. the trick here is disk_offset values are provided with "privoffset & puboffset" values delibaretely.

another point though it may not be relevant here, you are running base version of 5.0 which had lot many of bugs & were fixed later ... check out SORT website for latest patch matrix..

https://sort.symantec.com/patch/matrix

 

Gaurav

View solution in original post

4 REPLIES 4

Gaurav_S
Moderator
Moderator
   VIP    Certified

Hi Kuldeep,

initially when you encapsulated the disk, did you had a swap entry in your vfstab file ? as you can see there is no swapvol created in your vxprint output..

secondly, can you paste

# modinfo |grep -i vx

# vxdisk list c0t0d0s2

# vxdisk list c0t1d0s2

# df -k

# swap -l

 

I would like to know if the private region size & public region size are same on the two disks..

 

Gaurav

sam321
Level 4

swapvol was removed by me previously

root@CLFPAP06 # modinfo |grep -i vx
 29  137e648  37f28 320   1  vxdmp (VxVM 5.0-2006-05-11a: DMP Drive)
 31 7c002000 337840 321   1  vxio (VxVM 5.0-2006-05-11a I/O driver)
 33  13b27c8    d48 322   1  vxspec (VxVM 5.0-2006-05-11a control/st)
218 7b3df180    c30 318   1  vxportal (VxFS 5.0_REV-5.0A55_sol portal )
219 7aa00000 1ba6d0  21   1  vxfs (VxFS 5.0_REV-5.0A55_sol SunOS 5)
234 7abd0000   a178 319   1  fdd (VxQIO 5.0_REV-5.0A55_sol Quick )
 

root@CLFPAP06 # vxdisk list c0t0d0s2
Device:    c0t0d0s2
devicetag: c0t0d0
type:      auto
hostid:    GSMPAP07
disk:      name=rootdg01 id=1224692939.4.GSMPAP07
group:     name=rootdg id=1224692943.6.GSMPAP07
info:      format=sliced,privoffset=1,pubslice=3,privslice=4
flags:     online ready private autoconfig autoimport imported
pubpaths:  block=/dev/vx/dmp/c0t0d0s3 char=/dev/vx/rdmp/c0t0d0s3
privpaths: block=/dev/vx/dmp/c0t0d0s4 char=/dev/vx/rdmp/c0t0d0s4
guid:      -
udid:      SEAGATE%5FST973402SSUN72G%5FDISKS%5F303734383232394E57300000
site:      -
version:   2.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=3 offset=1 len=143267904 disk_offset=0
private:   slice=4 offset=1 len=81407 disk_offset=143267904
update:    time=1294126347 seqno=0.35
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
 

root@CLFPAP06 # vxdisk list c0t1d0s2
Device:    c0t1d0s2
devicetag: c0t1d0
type:      auto
hostid:    GSMPAP07
disk:      name=rootdg02 id=1294120876.18.GSMPAP07
group:     name=rootdg id=1224692943.6.GSMPAP07
info:      format=sliced,privoffset=1,pubslice=3,privslice=4
flags:     online ready private autoimport imported
pubpaths:  block=/dev/vx/dmp/c0t1d0s3 char=/dev/vx/rdmp/c0t1d0s3
privpaths: block=/dev/vx/dmp/c0t1d0s4 char=/dev/vx/rdmp/c0t1d0s4
guid:      -
udid:      SEAGATE%5FST973402SSUN72G%5FDISKS%5F303734383232394D4A4B0000
site:      -
version:   2.1
iosize:    min=512 (bytes) max=2048 (blocks)
public:    slice=3 offset=0 len=143267904 disk_offset=81408
private:   slice=4 offset=1 len=81407 disk_offset=0
update:    time=1294120881 seqno=0.7
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
c0t1d0s2        state=enabled
 

 

root@CLFPAP06 # df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/vx/dsk/bootdg/rootvol
                     20655025 14586323 5862152    72%    /
/devices                   0       0       0     0%    /devices
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                 21904624    1784 21902840     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
sharefs                    0       0       0     0%    /etc/dfs/sharetab
fd                         0       0       0     0%    /dev/fd
swap                 21903296     456 21902840     1%    /tmp
swap                 21902896      56 21902840     1%    /var/run
swap                 21902840       0 21902840     0%    /dev/vx/dmp
swap                 21902840       0 21902840     0%    /dev/vx/rdmp
97.253.16.165:/crm   10485760 8168336 2317424    78%    /u20/tuxedo
/dev/vx/dsk/rootdg/u14vol
                     5242880  327769 4608386     7%    /u14/clarify
/dev/vx/dsk/rootdg/u13vol
                     12582912 4706779 7397836    39%    /u13/weblogic
/dev/vx/dsk/rootdg/u01vol
                     6291456 1019965 4942051    18%    /u01/app/oracle/product/9.2.0
 

added swap again now

root@CLFPAP06 # swap -l
swapfile             dev  swaplo blocks   free
/dev/vx/dsk/rootdg/swapvol 321,113001     16 20972704 20972704
 

 

Gaurav_S
Moderator
Moderator
   VIP    Certified

ok, public & private region looks similar in both the disks...

Can your vxprint see a swapvol now ?  & are you getting the same error after issuing the same command ?

I would recommend to run vxmirror -g rootdg  (not vxassist mirror)..

If the above mirror fails, I see one more issue:

Notice the disk_offset values of two disks:

public:    slice=3 offset=1 len=143267904 disk_offset=0
private:   slice=4 offset=1 len=81407 disk_offset=143267904 <<<<<<<<<<<<<

public:    slice=3 offset=0 len=143267904 disk_offset=81408
private:   slice=4 offset=1 len=81407 disk_offset=0

though public & private region lengths are same however disk offset is different, it would be good  if you keep them same... this would be little tricky to initialize disk like this because you don't have any switch called  "disk_offset" to define in "vxdisksetup" command .. If you want to make these parameters similar, you have to do following:

-- Make sure which disk server is booted (prtconf -pv
 grep -i bootpath) lets assume it booted from rootdisk i.e c0t0d0

-- you can remove all the mirrors from rootmirror disk (use vxplex dis)

-- take rootmirror disk out of veritas (vxdg -g rootdg rmdisk) -- make sure you have deleted all the components from rootmirror disk. Take extra precaution before deleting, make sure there is no volume which is mounted from rootmirror disk

-- Reinitialize rootmirror again with following options:

# vxdisksetup -i c0t1d0  privlen=81407  privoffset=143267904  publen=143267904  puboffset=0  format=sliced pubslice=4 privslice=3

above command should make disk struncture of root mirror similar to rootdisk.. the trick here is disk_offset values are provided with "privoffset & puboffset" values delibaretely.

another point though it may not be relevant here, you are running base version of 5.0 which had lot many of bugs & were fixed later ... check out SORT website for latest patch matrix..

https://sort.symantec.com/patch/matrix

 

Gaurav

View solution in original post

sam321
Level 4

Hi gaurav

thanks for the info

will check tomorrow and let you know