<?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: fsadm in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012428#M426764</link>
    <description>The problem was that my math was incorrect.  I was expanding from 5 gig to 9 gig.  Boy do I feel stupid.  Thanks to everyone for the responses.  I love this forum!&lt;BR /&gt;Thanks!</description>
    <pubDate>Mon, 06 Nov 2006 13:11:37 GMT</pubDate>
    <dc:creator>nancy rippey</dc:creator>
    <dc:date>2006-11-06T13:11:37Z</dc:date>
    <item>
      <title>fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012422#M426758</link>
      <description>I am trying to extend a vxfs filesystem but my command keeps erroring out.  I have done this numerous times before and never had a problem.&lt;BR /&gt;This is an hpux 11.i server with OnLineJFS intalled.  I have extended my logical volume by 4 gig.  When I look at the lvsize it is correct. To extend the filesystem I am inputting&lt;BR /&gt;/usr/lbin/fs/vxfs/fsadm -F vxfs -b 5734400000 /software&lt;BR /&gt;and receiving the following message.  Any help would be greatly appreciated.&lt;BR /&gt;vxfs fsadm: Usage:&lt;BR /&gt;    fsadm [-F vxfs] [-V] [-b newsize] [-r rawdev] path_of_mountpoint&lt;BR /&gt;    fsadm [-F vxfs] [-V] [-DEcde] [-vs] [-a days] [-r rawdev] [-l largesize]&lt;BR /&gt;          [-p passes] [-t time] path_of_mountpoint&lt;BR /&gt;    fsadm [-F vxfs] [-o largefiles|nolargefiles] path_of_mountpoint|rawdev&lt;BR /&gt;    fsadm [-F vxfs] -c path_of_mountpoint&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Nov 2006 12:52:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012422#M426758</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2006-11-06T12:52:16Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012423#M426759</link>
      <description>What happens if you try..&lt;BR /&gt;&lt;BR /&gt;fsadm -F vxfs -b5000M (or newsize followed by M) /mountpoint&lt;BR /&gt;&lt;BR /&gt;-USA.</description>
      <pubDate>Mon, 06 Nov 2006 12:55:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012423#M426759</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2006-11-06T12:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012424#M426760</link>
      <description>If the filesystem is already mounted then the mountpoint is required. I would give it the -r rawdevice argument as well. However, I suspect that your real problems is one of two things: 1) You are missing a lost+found directory so that the .fsadm lock file cannot be written, or 2) (and most likely) the filesystem is completely full. There must be some spare root for fsadm -b to work.</description>
      <pubDate>Mon, 06 Nov 2006 13:00:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012424#M426760</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-11-06T13:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012425#M426761</link>
      <description>Have you tried extending thru SAM?</description>
      <pubDate>Mon, 06 Nov 2006 13:01:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012425#M426761</guid>
      <dc:creator>Sheriff Andy</dc:creator>
      <dc:date>2006-11-06T13:01:11Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012426#M426762</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Silly question, but did you lvextend the logical volume before running fsadm. Its necesary to do so.&lt;BR /&gt;&lt;BR /&gt;The command syntax seems okay.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 06 Nov 2006 13:03:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012426#M426762</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-11-06T13:03:33Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012427#M426763</link>
      <description>The fsadm use size in kb so your (5734400000) is too big for 4G.&lt;BR /&gt;Use 4*1024*1024 = 4194304&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Mon, 06 Nov 2006 13:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012427#M426763</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2006-11-06T13:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: fsadm</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012428#M426764</link>
      <description>The problem was that my math was incorrect.  I was expanding from 5 gig to 9 gig.  Boy do I feel stupid.  Thanks to everyone for the responses.  I love this forum!&lt;BR /&gt;Thanks!</description>
      <pubDate>Mon, 06 Nov 2006 13:11:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/fsadm/m-p/5012428#M426764</guid>
      <dc:creator>nancy rippey</dc:creator>
      <dc:date>2006-11-06T13:11:37Z</dc:date>
    </item>
  </channel>
</rss>

