<?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: lvextend syntax in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457344#M209573</link>
    <description>Great, that's what I thought.&lt;BR /&gt;&lt;BR /&gt;Thanks much!</description>
    <pubDate>Thu, 06 Jan 2005 16:04:31 GMT</pubDate>
    <dc:creator>Dead UserID_12</dc:creator>
    <dc:date>2005-01-06T16:04:31Z</dc:date>
    <item>
      <title>lvextend syntax</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457341#M209570</link>
      <description>Hello,&lt;BR /&gt;I need to increase the space available to a file system, my /opt filesystem, and have a question about the lvextend systax.&lt;BR /&gt;&lt;BR /&gt;I think I need to give lv the path to the physical volume because I need to be sure that lv does not use certain disks that contain raw data. My assumption is that lv will use the first available disk space it finds where it finds no file system or volume group and if it does that it would destroy all of the data on those raw disks used by a database application.&lt;BR /&gt;&lt;BR /&gt;So, please take a look at what I believe is the correct syntax:&lt;BR /&gt;&lt;BR /&gt;# lvextend -L 1000 /dev/vg00/lvol5 /dev/dsk/c7t12d0&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Thu, 06 Jan 2005 15:52:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457341#M209570</guid>
      <dc:creator>Dead UserID_12</dc:creator>
      <dc:date>2005-01-06T15:52:54Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend syntax</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457342#M209571</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If the space on the disk is being used by another lv, it won't be destroyed. &lt;BR /&gt;&lt;BR /&gt;However the command syntax that you have mentioned would extend the lv /dev/vg00/lvol5  on the disk /dev/dsk/c7t12d0.&lt;BR /&gt;&lt;BR /&gt;If the disk /dev/dsk/c7t12d0 doesn't have free space for this filesystem to get extended, it will error out.&lt;BR /&gt;&lt;BR /&gt;say the current size of /dev/vg00/lvol5 is 512MB and you want to increase it to 1000MB. the disk /dev/dsk/c7t12d0 must have 476MB free, else the command would error out. If there is that much space on the disk, the filesystem will get extended on that disk.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2005 16:00:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457342#M209571</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2005-01-06T16:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend syntax</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457343#M209572</link>
      <description>You don't have to worry about lvextend clobbering disks. A disk can only be used for LVOL PE's iff (if and only if) it has first been added to a volume group via vgcreate or vgextend and these commands must have been preceded by pvcreate. LVM knows nothing about filesystems so the presence of a filesystem is no protection. If an LVOL is used as a raw device, it too is "safe" from incursion by other LVM commands. You really only have to be careful when running the pvcreate command that you don't clobber raw disks or disks used for swap.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 06 Jan 2005 16:02:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457343#M209572</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-01-06T16:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend syntax</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457344#M209573</link>
      <description>Great, that's what I thought.&lt;BR /&gt;&lt;BR /&gt;Thanks much!</description>
      <pubDate>Thu, 06 Jan 2005 16:04:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457344#M209573</guid>
      <dc:creator>Dead UserID_12</dc:creator>
      <dc:date>2005-01-06T16:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend syntax</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457345#M209574</link>
      <description>That syntax is correct to extend lvol5 onto /dev/dsk/c7t12d0.  The disk needs enough room for the extended volume if not you will receive an error.&lt;BR /&gt;&lt;BR /&gt;You can list multiple PVs as destinations for an lvextend by listing the drives.  This would help if your volume needs to be larger than anyone drive.</description>
      <pubDate>Thu, 06 Jan 2005 16:06:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend-syntax/m-p/3457345#M209574</guid>
      <dc:creator>Gordon Bonnar</dc:creator>
      <dc:date>2005-01-06T16:06:40Z</dc:date>
    </item>
  </channel>
</rss>

