Mending VxVM

Last night I was upgrading a domain on our SF6900 box to Solaris 10 and since we use VxVM to mirror our root disk there was no use in preparing dedicated backup neither on tape nor on separate disk because it’s much easier and accurate to split rootdg into two disk groups, e.g. rootdg and rootdgold, and later import rootdgold, i.e. our saved copy of rootdg, to restore every single file. But when I tried to start the volumes it only revealed that not everything went off smoothly:

# vxvol -g rootdgold startall
VxVM vxvol ERROR V-5-1-11804 Volume coredump is empty and cannot be started
VxVM vxvol ERROR V-5-1-11804 Volume oem_home is empty and cannot be started
VxVM vxvol ERROR V-5-1-11804 Volume var is empty and cannot be started
VxVM vxvol ERROR V-5-1-11804 Volume rootvol is empty and cannot be started
VxVM vxvol ERROR V-5-1-11804 Volume swapvol is empty and cannot be started

Looking at the volumes I found that all of them were really in EMPTY state:

# vxprint -g rootdgold -v
TY NAME         ASSOC        KSTATE   LENGTH   PLOFFS   STATE    TUTIL0  PUTIL0
v  coredump     fsgen        DISABLED 62918208 -        EMPTY    -       -
v  oem_home     fsgen        DISABLED 4202688  -        EMPTY    -       -
v  rootvol      root         DISABLED 8395200  -        EMPTY    -       -
v  swapvol      swap         DISABLED 50330496 -        EMPTY    -       -
v  var          fsgen        DISABLED 8395200  -        EMPTY    -       -

Actually, not much should be done to overcome this situation. You could use both “vxvol init clean” or “vxmend fix clean” as a remedy to set the state for the named plex to CLEAN:

# vxmend -g rootdgold fix clean rootvol-02
# vxmend -g rootdgold fix clean coredump-02
# vxmend -g rootdgold fix clean oem_home-02
# vxmend -g rootdgold fix clean var-02
# vxmend -g rootdgold fix clean swap-02

Once that has been done I started the volume and successfully mounted it.

# vxvol -g rootdgold startall
Posted on January 21, 2010 at 5:46 pm by sergeyt · Permalink
In: Veritas

Leave a Reply