I was trying to upgrade Veritas Volume Manager from 3.5 to 4.1 when the upgrade script stopped and complained about a volume not in sync. It was a swap volume.

# vxprint -ht swapvol
Disk group: rootdg

v swapvol - ENABLED NEEDSYNC 8395200 ROUND - swap
pl swapvol-01 swapvol ENABLED ACTIVE 8395200 CONCAT - RW
sd rootdisk-01 swapvol-01 rootdisk 5159231 8395200 0 c0t8d0 ENA
pl swapvol-02 swapvol ENABLED ACTIVE 8395200 CONCAT - RW
sd disk01-04 swapvol-02 disk01 19853376 8395200 0 c1t8d0 ENA

To fix this problem, all I did was issue a resync.

# vxvol resync swapvol

# vxprint -ht swapvol
Disk group: rootdg

v swapvol - ENABLED ACTIVE 8395200 ROUND - swap
pl swapvol-01 swapvol ENABLED ACTIVE 8395200 CONCAT - RW
sd rootdisk-01 swapvol-01 rootdisk 5159231 8395200 0 c0t8d0 ENA
pl swapvol-02 swapvol ENABLED ACTIVE 8395200 CONCAT - RW
sd disk01-04 swapvol-02 disk01 19853376 8395200 0 c1t8d0 ENA
I just encounter a problem with permissions on raw volumes.  The raw volumes were used by a database and permissions on these volumes were set using chown and chmod.  However, when we failover, the permissions were not carried out.

So I used the veritas function to change the ownership and permission of the volumes.

# vxedit -g set user= group= mode=
Posted by JAUGHN Labels: ,
Visit the Site
MARVEL and SPIDER-MAN: TM & 2007 Marvel Characters, Inc. Motion Picture © 2007 Columbia Pictures Industries, Inc. All Rights Reserved. 2007 Sony Pictures Digital Inc. All rights reserved. blogger template by blog forum