<?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 issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071170#M307563</link>
    <description>Usually disk groups should get imported automatically on reboot according to their disks' host id.&lt;BR /&gt;Thus I can only conclude that the disk whose auto-import failed probably was tagged with another host's ID.&lt;BR /&gt;&lt;BR /&gt;You can esaily verify by&lt;BR /&gt;&lt;BR /&gt;# vxdisk list cXtXdX | grep hostid&lt;BR /&gt;&lt;BR /&gt;If it is not the same as a "uname -n" would produce, and if you are absolutely sure that this particular disk is not currently active in a disk group imported on another host,&lt;BR /&gt;you may clear the hostid tag by either&lt;BR /&gt;&lt;BR /&gt;# vxdisk clearimport cXtXdX&lt;BR /&gt;&lt;BR /&gt;or during import of the DG&lt;BR /&gt;&lt;BR /&gt;# vxdg -C dg_name&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Please, note that my VxVM experience is totally based on VxVM 3.5 under Solaris on Ultra SPARC, which may totally differ from HP's VxVM implementation.&lt;BR /&gt;So you better consult your manpages of vxdisk and vxdg before issueing any command!&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 17 Sep 2007 04:57:56 GMT</pubDate>
    <dc:creator>Ralph Grothe</dc:creator>
    <dc:date>2007-09-17T04:57:56Z</dc:date>
    <item>
      <title>vxvm issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071167#M307560</link>
      <description>Hi &lt;BR /&gt;  In one Hpux server I am seeing some disks as online invalid after importing forcefully since normal import failed.can any one tell me how to recover private region in those disks to make them online.</description>
      <pubDate>Sun, 16 Sep 2007 12:23:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071167#M307560</guid>
      <dc:creator>swarup kundu</dc:creator>
      <dc:date>2007-09-16T12:23:11Z</dc:date>
    </item>
    <item>
      <title>Re: vxvm issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071168#M307561</link>
      <description>Those "some disks" may belongs to a diskgroup which maybe "disabled" ?&lt;BR /&gt;&lt;BR /&gt;Can you post the results of the followings&lt;BR /&gt;# vxprint -ht&lt;BR /&gt;# vxprint -g &lt;DG&gt; -ht&lt;BR /&gt;# vxdg list&lt;BR /&gt;# vxdisk list&lt;BR /&gt;&lt;BR /&gt;I am wondering as why the diskgroup was imported forcefully? What errors did it give while importing it in normal/usual way? Something maybe wrong which needs to be fixed to make the diskgroup(s) enabled.&lt;BR /&gt;&lt;/DG&gt;</description>
      <pubDate>Sun, 16 Sep 2007 21:20:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071168#M307561</guid>
      <dc:creator>Sameer_Nirmal</dc:creator>
      <dc:date>2007-09-16T21:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: vxvm issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071169#M307562</link>
      <description>Hi,&lt;BR /&gt;If you see online invalid then your disk is not initialized by vxvm , perhaps if tou initialize the disk you will loose the data on the disk &lt;BR /&gt;&lt;BR /&gt;do vxdisk list diskname on the disk which you imported , if are able to see &lt;BR /&gt;group:     name=rootdg id=1186556662.1041.hostname &lt;BR /&gt;in vxdisk list diskname output you can import the disk group with &lt;BR /&gt;#vxdg import 1186556662.1041.hostname &lt;BR /&gt;Good Luck &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Javed Khan</description>
      <pubDate>Mon, 17 Sep 2007 01:14:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071169#M307562</guid>
      <dc:creator>Javed Khan_1</dc:creator>
      <dc:date>2007-09-17T01:14:57Z</dc:date>
    </item>
    <item>
      <title>Re: vxvm issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071170#M307563</link>
      <description>Usually disk groups should get imported automatically on reboot according to their disks' host id.&lt;BR /&gt;Thus I can only conclude that the disk whose auto-import failed probably was tagged with another host's ID.&lt;BR /&gt;&lt;BR /&gt;You can esaily verify by&lt;BR /&gt;&lt;BR /&gt;# vxdisk list cXtXdX | grep hostid&lt;BR /&gt;&lt;BR /&gt;If it is not the same as a "uname -n" would produce, and if you are absolutely sure that this particular disk is not currently active in a disk group imported on another host,&lt;BR /&gt;you may clear the hostid tag by either&lt;BR /&gt;&lt;BR /&gt;# vxdisk clearimport cXtXdX&lt;BR /&gt;&lt;BR /&gt;or during import of the DG&lt;BR /&gt;&lt;BR /&gt;# vxdg -C dg_name&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Please, note that my VxVM experience is totally based on VxVM 3.5 under Solaris on Ultra SPARC, which may totally differ from HP's VxVM implementation.&lt;BR /&gt;So you better consult your manpages of vxdisk and vxdg before issueing any command!&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Sep 2007 04:57:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vxvm-issue/m-p/4071170#M307563</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-09-17T04:57:56Z</dc:date>
    </item>
  </channel>
</rss>

