<?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: How to import volume group and it's logical volumes in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254441#M588461</link>
    <description>The problem is solved. Executing vgimport without any mapfile created vg01/lvol1.&lt;BR /&gt;After executing fsck -F vxfs -o full /dev/vg01/lvol1 it was possible to mount the logical volume in read/write mode. Before running fsck it was only possible to mount in read only mode.&lt;BR /&gt;&lt;BR /&gt;Thank you everyone, Lars</description>
    <pubDate>Fri, 22 Aug 2008 09:14:58 GMT</pubDate>
    <dc:creator>Lars Bylander</dc:creator>
    <dc:date>2008-08-22T09:14:58Z</dc:date>
    <item>
      <title>How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254431#M588451</link>
      <description>My L2000 (rp5450) server have 4 disks, 2 disks used for vg00 and 2 disks vg01. Due to failure in one of the disks used by vg00 I have repleaced the vg00 disks and reinstalled using ignit-ux. User data is located on the vg01 disks. I would appreciate some guidance how to import the vg01 disks si they can be used by the newly installed OS (version 11i). I do not have any LVM configuration backup.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Lars Bylander</description>
      <pubDate>Tue, 19 Aug 2008 11:20:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254431#M588451</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-19T11:20:50Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254432#M588452</link>
      <description>vgimport vg01 /dev/dsk/cUtVdW /dev/dsk/cXtYdZ&lt;BR /&gt;&lt;BR /&gt;Assuming your logical volumes used conventional names (lvol1, lvol2, etc), there is no need for a map file.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Tue, 19 Aug 2008 11:28:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254432#M588452</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2008-08-19T11:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254433#M588453</link>
      <description>If you know the disk which were there in vg01, then you can directly import the Volume Group.&lt;BR /&gt;&lt;BR /&gt;mkdir /dev/vg01&lt;BR /&gt;mknod /dev/vg01/group c 64 0x------&lt;BR /&gt;vgcreate&lt;BR /&gt;vgimport /dev/vg01 disk name&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;SKR</description>
      <pubDate>Tue, 19 Aug 2008 11:36:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254433#M588453</guid>
      <dc:creator>SKR_1</dc:creator>
      <dc:date>2008-08-19T11:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254434#M588454</link>
      <description>Thank you for your comments.&lt;BR /&gt;&lt;BR /&gt;Will vgimport write anything to the disks to be imported? or is only /etc/lvmtab and eventually /etc/lvmconfig updated?&lt;BR /&gt;&lt;BR /&gt;Executing vgimport with the option preview:&lt;BR /&gt;vgimport -m /tmp/vg01.mapfile -p -v /dev/vg01 /dev/dsk/c2t0d0 /dev/dsk/c1t0d0&lt;BR /&gt;Beginning the import process on Volume Group "/dev/vg01".&lt;BR /&gt;Logical volume "/dev/vg01/lvol20" has been successfully created&lt;BR /&gt;with lv number 1.&lt;BR /&gt;Logical volume "/dev/vg01/lvol21" has been successfully created&lt;BR /&gt;with lv number 1.&lt;BR /&gt;Volume group "/dev/vg01" has been successfully created.&lt;BR /&gt;&lt;BR /&gt;The map files used where a copy of the mapfile: /etc/lvmconf/vg01.mapfile&lt;BR /&gt;Strange that lv number 1 points to 2 logical volumes!!&lt;BR /&gt;&lt;BR /&gt;Best regards.&lt;BR /&gt;Lars</description>
      <pubDate>Wed, 20 Aug 2008 09:51:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254434#M588454</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-20T09:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254435#M588455</link>
      <description>What is the contents of your mapfile?</description>
      <pubDate>Wed, 20 Aug 2008 11:08:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254435#M588455</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-20T11:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254436#M588456</link>
      <description>The contents of the map file is:&lt;BR /&gt;# cat /tmp/vg01.mapfile&lt;BR /&gt;1 lvol20&lt;BR /&gt;1 lvol21&lt;BR /&gt;&lt;BR /&gt;/Lars</description>
      <pubDate>Wed, 20 Aug 2008 11:52:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254436#M588456</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-20T11:52:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254437#M588457</link>
      <description>This is the problem - should be like this:&lt;BR /&gt;&lt;BR /&gt;# cat /tmp/vg01.mapfile&lt;BR /&gt;1 lvol20&lt;BR /&gt;2 lvol21&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;IMHO you don't need a mapfile for your config, unless the lvols should be not named lvol1 and lvol2.&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Aug 2008 11:59:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254437#M588457</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-20T11:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254438#M588458</link>
      <description>Hi Lars:&lt;BR /&gt;&lt;BR /&gt;As Torsten notes, the mapfile is useful when your logical volume names are *not* standard (i.e. are not 'lvol1', 'lvol2', etc. associated with logical volume #1 and #2, respectively).&lt;BR /&gt;&lt;BR /&gt;However, there is another use of the mapfile, and that is to contain the Volume Group ID (VGID) of the physical disks comprising the volume group.  If this is included (by specifying '-s' during 'vgexport' *and* during the subsequent 'vgimport'), then you can avoid having to specify the device files (pv_paths) during the process.  The VGID disk signiture is read instead and and all physical disks with a matching VGID collected into a volume group.&lt;BR /&gt;&lt;BR /&gt;This is particularly useful during cold-installations or when disk are moved among servers, or when SANs are rezoned, since one doesn't have to look up pv_paths for the affected disks.&lt;BR /&gt;&lt;BR /&gt;See the manpages for 'vgexport' and 'vgimport' for more information.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Aug 2008 12:18:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254438#M588458</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2008-08-20T12:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254439#M588459</link>
      <description>Hi James,&lt;BR /&gt;&lt;BR /&gt;Well I had a disk crash and did not have anything saved from vgexport. Some earlier LVM setup seems to have generated the strange mapfile:&lt;BR /&gt;&lt;BR /&gt;# cat /etc/lvmconf/vg01.mapfile&lt;BR /&gt;1 lvol20&lt;BR /&gt;1 lvol21&lt;BR /&gt;&lt;BR /&gt;After executing vgimport with preview I think that lvol20 and lvol21 are treated as the same logical volumes.&lt;BR /&gt;&lt;BR /&gt;Anyway, since I do not want risk that data on the vg01 disks are destroyed, does vgimport only write to the config files in /etc?&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Aug 2008 12:30:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254439#M588459</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-20T12:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254440#M588460</link>
      <description>If you are not sure about the mapfile - leave it away and try without.&lt;BR /&gt;&lt;BR /&gt;vgimport -p ...&lt;BR /&gt;&lt;BR /&gt;will preview the results.</description>
      <pubDate>Wed, 20 Aug 2008 12:38:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254440#M588460</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-08-20T12:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254441#M588461</link>
      <description>The problem is solved. Executing vgimport without any mapfile created vg01/lvol1.&lt;BR /&gt;After executing fsck -F vxfs -o full /dev/vg01/lvol1 it was possible to mount the logical volume in read/write mode. Before running fsck it was only possible to mount in read only mode.&lt;BR /&gt;&lt;BR /&gt;Thank you everyone, Lars</description>
      <pubDate>Fri, 22 Aug 2008 09:14:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254441#M588461</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-22T09:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254442#M588462</link>
      <description>Lars:"Due to failure in one of the disks used by vg00 I have replaced the vg00 disks and reinstalled using ignit-ux."&lt;BR /&gt;&lt;BR /&gt;Uh...glad you got it resolved, but it seems you have no mirroring? The L2000 "internal" disks are hot-swappable, and you *shouldn't* have needed to Ignite the box...shouldn't have had any downtime at all. &lt;BR /&gt;&lt;BR /&gt;If not already installed, consider licensing / installing MirrorDisk.</description>
      <pubDate>Fri, 22 Aug 2008 14:51:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254442#M588462</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2008-08-22T14:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to import volume group and it's logical volumes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254443#M588463</link>
      <description>Hello Oldschool,&lt;BR /&gt;&lt;BR /&gt;You got a point and I will check the license cost.&lt;BR /&gt;&lt;BR /&gt;Thanks, Lars</description>
      <pubDate>Mon, 25 Aug 2008 05:28:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/how-to-import-volume-group-and-it-s-logical-volumes/m-p/4254443#M588463</guid>
      <dc:creator>Lars Bylander</dc:creator>
      <dc:date>2008-08-25T05:28:30Z</dc:date>
    </item>
  </channel>
</rss>

