<?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 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845352#M92062</link>
    <description>This will give you the explanation:&lt;BR /&gt;&lt;BR /&gt;# man fsadm_vxfs&lt;BR /&gt;&lt;BR /&gt;The number after -b is the new size sector number.  And yes these parameters and even commands depend on file system types.</description>
    <pubDate>Thu, 14 Nov 2002 22:05:16 GMT</pubDate>
    <dc:creator>Helen French</dc:creator>
    <dc:date>2002-11-14T22:05:16Z</dc:date>
    <item>
      <title>lvextend</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845351#M92061</link>
      <description>i was looking at the SAM logs after increasing the size of the file system..&lt;BR /&gt;&lt;BR /&gt;it executes &lt;BR /&gt;fasadm -F vxfs -b 770048 /var&lt;BR /&gt;&lt;BR /&gt;how is this no 770048 calculated and what does it mean?? Also, does this no depend on the type of filesystem??</description>
      <pubDate>Thu, 14 Nov 2002 21:54:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845351#M92061</guid>
      <dc:creator>roadrunner_1</dc:creator>
      <dc:date>2002-11-14T21:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845352#M92062</link>
      <description>This will give you the explanation:&lt;BR /&gt;&lt;BR /&gt;# man fsadm_vxfs&lt;BR /&gt;&lt;BR /&gt;The number after -b is the new size sector number.  And yes these parameters and even commands depend on file system types.</description>
      <pubDate>Thu, 14 Nov 2002 22:05:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845352#M92062</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-11-14T22:05:16Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845353#M92063</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Sectors are normally 512 bytes.&lt;BR /&gt;You can verify using&lt;BR /&gt;diskinfo /dev/rdsk/cxtydz&lt;BR /&gt;on that drive.&lt;BR /&gt;So by my calculations you increased /var to&lt;BR /&gt;394,264,576 bytes - correct?&lt;BR /&gt;&lt;BR /&gt;Rgds,&lt;BR /&gt;Jeff</description>
      <pubDate>Thu, 14 Nov 2002 22:07:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845353#M92063</guid>
      <dc:creator>Jeff Schussele</dc:creator>
      <dc:date>2002-11-14T22:07:26Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845354#M92064</link>
      <description>*********No points will be assigned for answers hereafter***********</description>
      <pubDate>Thu, 14 Nov 2002 22:17:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845354#M92064</guid>
      <dc:creator>roadrunner_1</dc:creator>
      <dc:date>2002-11-14T22:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: lvextend</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845355#M92065</link>
      <description>:-)&lt;BR /&gt;&lt;BR /&gt;I like this approach! Will serve the purpose till Dan and his team put this feature for us.</description>
      <pubDate>Thu, 14 Nov 2002 22:28:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvextend/m-p/2845355#M92065</guid>
      <dc:creator>Kellogg Unix Team</dc:creator>
      <dc:date>2002-11-14T22:28:04Z</dc:date>
    </item>
  </channel>
</rss>

