Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

old_rootvg appears, but there's no hdisk in it

Status
Not open for further replies.

MoreFeo

Technical User
Nov 29, 2002
547
ES
Hi, I've got some servers that show that old_rootvg exist (when issuing lsvg), but when I do lspv there is no hdisk associated with it.

I didn't install these servers, so I don't know what happened, but I suppose someone did an alt_disk_install/alt_disk_mksysb and rebooted from the new alt_rootvg, then deleted the old_rootvg hdisk without executing alt_rootvg_op -X.

I'm trying to delete the old_rootvg with "alt_rootvg_op -X old_rootvg" but it's failing:
Code:
# lsvg
old_rootvg
rootvg
swapvg
ESP.datavg
# lspv
hdisk2    00c974954896d012        rootvg        active
hdisk3    00c974954896d120        swapvg        active
hdisk5    00c9749549340ace        ESP.datavg    active
# alt_rootvg_op -X old_rootvg
0505-105 alt_disk_install: Bad argument: old_rootvg for option -X.
Usage alt_rootvg_op: Determine Volume Group Boot Disk (-q):
      alt_rootvg_op -q -d <disk> [-D]

Usage alt_rootvg_op: Rename Alternate Disk Volume Group (-v):
      alt_rootvg_op -v <new volume group name> -d <disk> [-D]

Usage alt_rootvg_op: Wake-up Volume Group (-W):
      alt_rootvg_op -W -d <disk> [-D]

Usage alt_rootvg_op: Put-to-sleep Volume Group (-S):
      alt_rootvg_op -S [-tD]

Usage alt_rootvg_op: Clean Up Alternate Disk Volume Group (-X):
      alt_rootvg_op -X [<volume group>] [-D]

Usage alt_rootvg_op: Customize Alternate Disk Volume Group (-C):
      alt_rootvg_op -C [-R <resolv_conf>] [-s <script>]
                       [-b <bundle_name>] [-I <installp_flags>]
                       [-l <images_location>] [-f <fix_bundle>]
                       [-F <fixes>] [-w <filesets>] [-DV]

Has anyone had this same situation?
I'm thinking maybe exporting the old_rootvg, or deleting from the ODM all the old_rootvg entries.
What do you think?

Thanks
 
I've searched for old_rootvg in the ODM and there are only a few entries:
In CuAt:
Code:
CuAt:
        name = "old_rootvg"
        attribute = "vgserial_id"
        value = "0009562c0000d6000000010fa0413015"
        type = "R"
        generic = "D"
        rep = "n"
        nls_index = 637

CuAt:
        name = "old_rootvg"
        attribute = "timestamp"
        value = "47681c661c01e677"
        type = "R"
        generic = "DU"
        rep = "s"
        nls_index = 0

CuAt:
        name = "old_rootvg"
        attribute = "pv"
        value = "0009562ca0410c040000000000000000"
        type = "R"
        generic = ""
        rep = "sl"
        nls_index = 0

CuAt:
        name = "old_rootvg"
        attribute = "auto_on"
        value = "n"
        type = "R"
        generic = "DU"
        rep = "l"
        nls_index = 638

In CuDv:
Code:
CuDv:
        name = "old_rootvg"
        status = 0
        chgstatus = 1
        ddins = ""
        location = ""
        parent = ""
        connwhere = ""
        PdDvLn = "logical_volume/vgsubclass/vgtype"

I've also searched for 0009562c0000d6000000010fa0413015 and 0009562ca0410c040000000000000000, but there are no more entries.

Do you think I can delete these entries from the ODM without problems, and that this will solve my problem?

Thanks.
 
An [tt]exportvg old_rootvg[/tt] should clean that up nicely.

But just make sure you have a backup copy of [tt]/etc/filesystems[/tt] because I read somewhere that exportvg old_rootvg *may* remove the real FS stanzas for the filesystems in your real rootvg.

You may want to do this on a server that can go wrong (sandbox or something)


HTH,

p5wizard
 
Thanks p5wizard, I've also read that exportvg could mess with /etc/filesystems.

I will try it and let you know.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top