<?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: vgimport fails in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271413#M33843</link>
    <description>is that you baby!!? Nice to to you trying to help. vgchgid is a hp-ux tool. there is no such easy tool in linux. &lt;BR /&gt;&lt;BR /&gt;This is fixed now .&lt;BR /&gt;pvscan,vgscan,"vgexport vgname"(it was already exported though and given the message that vgexport failed; But indeed that made a difference). then vgimport that helped.&lt;BR /&gt;&lt;BR /&gt;it was reporing that some other vg was using the same group number. But in linux we dont create group file maually. Linux does that itself.&lt;BR /&gt;&lt;BR /&gt;So i guess the same  steps should help again.</description>
    <pubDate>Fri, 19 Sep 2008 17:40:09 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2008-09-19T17:40:09Z</dc:date>
    <item>
      <title>vgimport fails</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271410#M33840</link>
      <description>&lt;BR /&gt;Red Hat Enterprise Linux AS release 3 (Taroon Update 9)&lt;BR /&gt;Linux hostname 2.4.21-53.ELsmp #1 SMP Wed Nov 14 03:54:12 EST 2007 i686 i686 i386 GNU/Linux&lt;BR /&gt;&lt;BR /&gt;lvm-1.0.8-14&lt;BR /&gt;&lt;BR /&gt;# vgimport -v --force /dev/sdn /dev/sdo /dev/sdp /dev/sdq /dev/sdr&lt;BR /&gt;vgimport -- locking logical volume manager&lt;BR /&gt;vgimport -- checking volume group name&lt;BR /&gt;vgimport -- checking volume group "sdn" existence&lt;BR /&gt;vgimport -- trying to read physical volumes&lt;BR /&gt;vgimport -- checking for duplicate physical volumes&lt;BR /&gt;vgimport -- checking physical volume name "/dev/sdo"&lt;BR /&gt;vgimport -- reading data of physical volume "/dev/sdo" from disk&lt;BR /&gt;vgimport -- checking for exported physical volume "/dev/sdo"&lt;BR /&gt;vgimport -- checking consistency of physical volume "/dev/sdo"&lt;BR /&gt;vgimport -- reallocating memory&lt;BR /&gt;vgimport -- checking for duplicate physical volumes&lt;BR /&gt;vgimport -- checking physical volume name "/dev/sdp"&lt;BR /&gt;vgimport -- reading data of physical volume "/dev/sdp" from disk&lt;BR /&gt;vgimport -- checking for exported physical volume "/dev/sdp"&lt;BR /&gt;vgimport -- checking consistency of physical volume "/dev/sdp"&lt;BR /&gt;vgimport -- reallocating memory&lt;BR /&gt;vgimport -- checking for duplicate physical volumes&lt;BR /&gt;vgimport -- checking physical volume name "/dev/sdq"&lt;BR /&gt;vgimport -- reading data of physical volume "/dev/sdq" from disk&lt;BR /&gt;vgimport -- checking for exported physical volume "/dev/sdq"&lt;BR /&gt;vgimport -- checking consistency of physical volume "/dev/sdq"&lt;BR /&gt;vgimport -- reallocating memory&lt;BR /&gt;vgimport -- checking for duplicate physical volumes&lt;BR /&gt;vgimport -- checking physical volume name "/dev/sdr"&lt;BR /&gt;vgimport -- reading data of physical volume "/dev/sdr" from disk&lt;BR /&gt;vgimport -- checking for exported physical volume "/dev/sdr"&lt;BR /&gt;vgimport -- checking consistency of physical volume "/dev/sdr"&lt;BR /&gt;vgimport -- reallocating memory&lt;BR /&gt;vgimport -- physical volumes "/dev/sdr" and "/dev/sdo" are in different volume groups&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I am restoring the data to these LUNS and when tried to import it fails.. Do you think those disks are having different header info( might have been used for diferent VG earlier; NOT sure) and a pvcreate will help here? do restore after the pvcreate?&lt;BR /&gt;Backup goes to tape using "dump" command (netapps snap volume goes to tape) and "retsore" command to restore to the LUNs.&lt;BR /&gt;&lt;BR /&gt;if the dump and restore preserving the pvid/vgid information while restore i am not sure why this two luns complaints so.&lt;BR /&gt;&lt;BR /&gt;any suggestions?</description>
      <pubDate>Wed, 17 Sep 2008 19:04:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271410#M33840</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-09-17T19:04:06Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport fails</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271411#M33841</link>
      <description>Hi,&lt;BR /&gt;"might have been used for diferent VG earlier"- No its not.&lt;BR /&gt;If you are importing then it is not related to That.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Gokul Chandola</description>
      <pubDate>Thu, 18 Sep 2008 07:48:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271411#M33841</guid>
      <dc:creator>Gokul Chandola</dc:creator>
      <dc:date>2008-09-18T07:48:40Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport fails</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271412#M33842</link>
      <description>physical volumes "/dev/sdr" and "/dev/sdo" are in different volume groups&lt;BR /&gt;&lt;BR /&gt;VGID is different on these Luns. use vgid command which u have used in  SBI......&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 19 Sep 2008 10:55:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271412#M33842</guid>
      <dc:creator>Sandeep_Chaudhary</dc:creator>
      <dc:date>2008-09-19T10:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport fails</title>
      <link>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271413#M33843</link>
      <description>is that you baby!!? Nice to to you trying to help. vgchgid is a hp-ux tool. there is no such easy tool in linux. &lt;BR /&gt;&lt;BR /&gt;This is fixed now .&lt;BR /&gt;pvscan,vgscan,"vgexport vgname"(it was already exported though and given the message that vgexport failed; But indeed that made a difference). then vgimport that helped.&lt;BR /&gt;&lt;BR /&gt;it was reporing that some other vg was using the same group number. But in linux we dont create group file maually. Linux does that itself.&lt;BR /&gt;&lt;BR /&gt;So i guess the same  steps should help again.</description>
      <pubDate>Fri, 19 Sep 2008 17:40:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/vgimport-fails/m-p/4271413#M33843</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-09-19T17:40:09Z</dc:date>
    </item>
  </channel>
</rss>

