<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: VxVM /dev/vx recovery in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101586#M600094</link>
    <description>Good suggestions, both, but ....&lt;BR /&gt;&lt;BR /&gt;You can't umount a filesystem if the device files for the volume don't exist anymore.&lt;BR /&gt;&lt;BR /&gt;No backup yet.  It took over a week to load the system, set up the 16TB of disk and restore data from tape.  I was just cleaning up in prep for a backup when I did the rm -fr /dev/ .&lt;BR /&gt;&lt;BR /&gt;I figure I can always re-import the non rootdg disk groups and volumes after a reboot.  I am worried about the  booting of the system without the bootdg/rootdg /dev/vx/rootdg/dsk files and the subsequent recovery.  I know the information is somewhere in the running system, I was just hoping there was someway to get the device file information out of VxVM.</description>
    <pubDate>Sun, 06 Apr 2008 14:24:28 GMT</pubDate>
    <dc:creator>Robert Klute</dc:creator>
    <dc:date>2008-04-06T14:24:28Z</dc:date>
    <item>
      <title>VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101583#M600091</link>
      <description>OK, I fat fingered a rm -fr.  I have recovered almost everything.  All I have left is rebuilding the VxVM device files.&lt;BR /&gt;&lt;BR /&gt;I am running 11.31 with VxVM, no LVM. I haven't rebooted so everything appears to still be working. Even so, I think it is kind of important to do rebuild the device files.&lt;BR /&gt;&lt;BR /&gt;Is there some way to rebuild the /dev/vx directory.  Before I reboot would be nice, in maintenance mode after reboot if necessary.  BTW, this does mean that /dev/vx/dsk/rootdg is gone.&lt;BR /&gt;&lt;BR /&gt;Thx.</description>
      <pubDate>Sat, 05 Apr 2008 00:43:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101583#M600091</guid>
      <dc:creator>Robert Klute</dc:creator>
      <dc:date>2008-04-05T00:43:16Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101584#M600092</link>
      <description>&lt;BR /&gt;I am not sure about rootdg, but for other DG's , You get the  configuration back by doing a deport and import the DG's. This will created disk group directories and related files.&lt;BR /&gt;&lt;BR /&gt;#vxdg deport &lt;DGNAME&gt;&lt;BR /&gt;#vxdg import &lt;DGNAME&gt;&lt;BR /&gt;&lt;BR /&gt;And I think once u boot in maintenance mode , u can recover rootdg config as well.&lt;/DGNAME&gt;&lt;/DGNAME&gt;</description>
      <pubDate>Sat, 05 Apr 2008 07:28:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101584#M600092</guid>
      <dc:creator>Siju Vadakkan</dc:creator>
      <dc:date>2008-04-05T07:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101585#M600093</link>
      <description>Hi Robert,&lt;BR /&gt;&lt;BR /&gt;Why not restore the device files from your backup or make_tape_recovery image.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Sat, 05 Apr 2008 19:17:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101585#M600093</guid>
      <dc:creator>Robert-Jan Goossens_1</dc:creator>
      <dc:date>2008-04-05T19:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101586#M600094</link>
      <description>Good suggestions, both, but ....&lt;BR /&gt;&lt;BR /&gt;You can't umount a filesystem if the device files for the volume don't exist anymore.&lt;BR /&gt;&lt;BR /&gt;No backup yet.  It took over a week to load the system, set up the 16TB of disk and restore data from tape.  I was just cleaning up in prep for a backup when I did the rm -fr /dev/ .&lt;BR /&gt;&lt;BR /&gt;I figure I can always re-import the non rootdg disk groups and volumes after a reboot.  I am worried about the  booting of the system without the bootdg/rootdg /dev/vx/rootdg/dsk files and the subsequent recovery.  I know the information is somewhere in the running system, I was just hoping there was someway to get the device file information out of VxVM.</description>
      <pubDate>Sun, 06 Apr 2008 14:24:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101586#M600094</guid>
      <dc:creator>Robert Klute</dc:creator>
      <dc:date>2008-04-06T14:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101587#M600095</link>
      <description>Hi Robert,&lt;BR /&gt;&lt;BR /&gt;Try below steps.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://seer.support.veritas.com/docs/266847.htm" target="_blank"&gt;http://seer.support.veritas.com/docs/266847.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;step 11&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Apr 2008 16:12:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101587#M600095</guid>
      <dc:creator>Robert-Jan Goossens_1</dc:creator>
      <dc:date>2008-04-06T16:12:49Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101588#M600096</link>
      <description>I think I figured out how to restore /dev.&lt;BR /&gt;&lt;BR /&gt;First 'insf -e' will restore the traditional device files.  Then you need to take care of the VxVM structure. I had a simple one - I didn't have clusters to deal with. &lt;BR /&gt;&lt;BR /&gt;recreate the vx directory&lt;BR /&gt;mkdir /dev/vx&lt;BR /&gt;&lt;BR /&gt;/dev/vx has 9 device files, &lt;BR /&gt;the major number is gotten from lsdev &lt;BR /&gt;look for 'vols vxvm' and 'dmp vxvm'.&lt;BR /&gt;They device files are&lt;BR /&gt;   Major type vols: (minor devname)&lt;BR /&gt;   0 config&lt;BR /&gt;   1 trace&lt;BR /&gt;   2 iod&lt;BR /&gt;   3 info&lt;BR /&gt;   4 task&lt;BR /&gt;   5 taskmon&lt;BR /&gt;   6 clust&lt;BR /&gt;   7 netiod&lt;BR /&gt;&lt;BR /&gt;   Major Type dmp&lt;BR /&gt;   0x03fffff dmpconfig&lt;BR /&gt;&lt;BR /&gt;Make the following directories under /dev/vx &lt;BR /&gt;   dmp dsk rdmp rdsk&lt;BR /&gt;&lt;BR /&gt;- dmp and rdmp contain the device files.&lt;BR /&gt;&lt;BR /&gt;Populate the dmp and rdmp directories&lt;BR /&gt;'vxdisk scandisks' will rebuild them&lt;BR /&gt;&lt;BR /&gt;- dsk and rdsk contain the volumes.&lt;BR /&gt;&lt;BR /&gt;Populate the volume device files.&lt;BR /&gt;&lt;BR /&gt;The volume devices are of the form&lt;BR /&gt;/dev/vx/dsk/&lt;DG&gt;/&lt;VOL&gt;&lt;BR /&gt;&lt;BR /&gt;For the rootdg there is also a symbolic link&lt;BR /&gt;/dev/vx/dsk/bootdg to /dev/vx/dsk/rootdg&lt;BR /&gt;&lt;BR /&gt;The volumes and their major and minor numbers can be gotten from files under /etc/vx/cbr/bk.  There you will find a directory for each dg in the form &lt;DG&gt;.&lt;X&gt;.&lt;Y&gt;.&lt;HOSTNAME&gt;.  In each directory is a file &lt;X&gt;.&lt;Y&gt;.&lt;HOSTNAME&gt;.cfgrec.  grep the file for '^vol ', 'node_bdev=', and 'node_cdev'.  You will get a series of entries like:&lt;BR /&gt;&lt;BR /&gt;vol  homevol&lt;BR /&gt;        node_bdev=4/5619004&lt;BR /&gt;        node_cdev=130/5619004&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From that you can make the device file for homevol:&lt;BR /&gt;&lt;BR /&gt;mknod /dev/vx/dsk/rootdg/homevol b 4 5619004&lt;BR /&gt;mknod /dev/vx/rdsk/rootdg/homevol c 130 5619004&lt;BR /&gt;&lt;/HOSTNAME&gt;&lt;/Y&gt;&lt;/X&gt;&lt;/HOSTNAME&gt;&lt;/Y&gt;&lt;/X&gt;&lt;/DG&gt;&lt;/VOL&gt;&lt;/DG&gt;</description>
      <pubDate>Sun, 06 Apr 2008 21:49:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101588#M600096</guid>
      <dc:creator>Robert Klute</dc:creator>
      <dc:date>2008-04-06T21:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: VxVM /dev/vx recovery</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101589#M600097</link>
      <description>See above post</description>
      <pubDate>Tue, 08 Apr 2008 15:47:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-dev-vx-recovery/m-p/5101589#M600097</guid>
      <dc:creator>Robert Klute</dc:creator>
      <dc:date>2008-04-08T15:47:17Z</dc:date>
    </item>
  </channel>
</rss>

