<?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: Expanding root file system in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230645#M553205</link>
    <description>Tom,&lt;BR /&gt;&lt;BR /&gt;I think that would work.  The usual roadblock is that /stand, swap and / have to be contiuous, but, if you move or shrink lvol4 (/tmp), before growing lvol3, you should be OK.&lt;BR /&gt;&lt;BR /&gt;However, I have to think that just doing an Ignite make_tap_recovery and rebuilding from that might be easier in the long run.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
    <pubDate>Wed, 17 Mar 2010 15:34:01 GMT</pubDate>
    <dc:creator>Pete Randall</dc:creator>
    <dc:date>2010-03-17T15:34:01Z</dc:date>
    <item>
      <title>Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230644#M553204</link>
      <description>I've got a server that the root mirror was broke to gain space and I'm trying to clean it up and remirror.&lt;BR /&gt;&lt;BR /&gt;/ is very small &lt;BR /&gt;/tmp is very large, and now spread across both local disks.&lt;BR /&gt;&lt;BR /&gt;There are three disks in the vg00&lt;BR /&gt;c0t6d0 a 73GB local disk,&lt;BR /&gt;c6t6d0 a 73GB local disk, and &lt;BR /&gt;c64t5d3 a 8GB SAN LUN.&lt;BR /&gt;&lt;BR /&gt;/dev/dsk/c0t6d0&lt;BR /&gt;   --- Distribution of physical volume ---&lt;BR /&gt;   LV Name            LE of LV  PE for LV&lt;BR /&gt;   /dev/vg00/lvol1    19        19&lt;BR /&gt;   /dev/vg00/lvol2    256       256&lt;BR /&gt;   /dev/vg00/lvol3    13        13&lt;BR /&gt;   /dev/vg00/lvol4    13        13&lt;BR /&gt;   /dev/vg00/lvol5    192       192&lt;BR /&gt;   /dev/vg00/lvol6    384       384&lt;BR /&gt;   /dev/vg00/lvol7    201       201&lt;BR /&gt;   /dev/vg00/lvol8    576       576&lt;BR /&gt;   /dev/vg00/lvol9    1952      1952&lt;BR /&gt;   /dev/vg00/lvol10   768       768&lt;BR /&gt;&lt;BR /&gt;/dev/dsk/c6t6d0&lt;BR /&gt;   --- Distribution of physical volume ---&lt;BR /&gt;   LV Name            LE of LV  PE for LV&lt;BR /&gt;   /dev/vg00/lvol4    487       487&lt;BR /&gt;   /dev/vg00/lvol9    288       288&lt;BR /&gt;&lt;BR /&gt;bdf |grep vg00&lt;BR /&gt;/dev/vg00/lvol3     212992  190976   21928   90% /&lt;BR /&gt;/dev/vg00/lvol1     298928   45568  223464   17% /stand&lt;BR /&gt;/dev/vg00/lvol8    9437184 6426824 2989392   68% /var&lt;BR /&gt;/dev/vg00/lvol7    3293184 2554392  733048   78% /usr&lt;BR /&gt;/dev/vg00/lvol9    36700160 29003552 7604144   79% /u01&lt;BR /&gt;/dev/vg00/lvol4    8192000  313488 7817152    4% /tmp&lt;BR /&gt;/dev/vg00/lvol6    6291456 4188488 2086576   67% /opt&lt;BR /&gt;/dev/vg00/lvol5    3145728 2341184  804544   74% /home&lt;BR /&gt;&lt;BR /&gt;My plan is to copy /u01 to a new SAN LUN and get it out of vg00.&lt;BR /&gt;Then mirror /tmp (lvol4) to c64t5d3.  I was going to break the mirror and then mirror it back to c0t6d0.&lt;BR /&gt;Before I do that I'd like to expand / (lvol3). Can I pull this off?  Lvol4 is right after lvol3, so if I've moved it to SAN disk can't I grow / without a restore from ignite?  Then I would mirror lovl4 back to the root disk and re-establish mirroring.  &lt;BR /&gt;</description>
      <pubDate>Wed, 17 Mar 2010 15:29:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230644#M553204</guid>
      <dc:creator>Tom Ward_1</dc:creator>
      <dc:date>2010-03-17T15:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230645#M553205</link>
      <description>Tom,&lt;BR /&gt;&lt;BR /&gt;I think that would work.  The usual roadblock is that /stand, swap and / have to be contiuous, but, if you move or shrink lvol4 (/tmp), before growing lvol3, you should be OK.&lt;BR /&gt;&lt;BR /&gt;However, I have to think that just doing an Ignite make_tap_recovery and rebuilding from that might be easier in the long run.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 17 Mar 2010 15:34:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230645#M553205</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2010-03-17T15:34:01Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230646#M553206</link>
      <description>I agree, but it is almost impossible to get down time for this system.  I've been trying for months.  Even now I can't reboot it after it gets mirrored.  Maybe next month if I'm lucky.  You can see why I want it mirrored.</description>
      <pubDate>Wed, 17 Mar 2010 15:49:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230646#M553206</guid>
      <dc:creator>Tom Ward_1</dc:creator>
      <dc:date>2010-03-17T15:49:27Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230647#M553207</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You can't get down time because it's a critical server in production?  Then I think a whole lot of people would be curious about anything that you did on that box, and especially curious if it was an unsanctioned from the manufacturer procedure.&lt;BR /&gt;&lt;BR /&gt;If I did it, and I have before when installing patches or making changes that don't require a reboot, and are transparent to the DBA's and SAP Admins, then I would tell no one.  And hope no one notices.&lt;BR /&gt;&lt;BR /&gt;Changing file systems vg's, I think someone would notice.</description>
      <pubDate>Wed, 17 Mar 2010 16:30:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230647#M553207</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2010-03-17T16:30:29Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230648#M553208</link>
      <description>I don't do changes without going through change control.  This isn't something that being done on the side or under the table.  I don't know what gave you that impression. &lt;BR /&gt;&lt;BR /&gt;I wouldn't take a chance doing something like this without an approved change request to cover things.</description>
      <pubDate>Wed, 17 Mar 2010 17:15:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230648#M553208</guid>
      <dc:creator>Tom Ward_1</dc:creator>
      <dc:date>2010-03-17T17:15:22Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230649#M553209</link>
      <description>Hi, Tom - &lt;BR /&gt;&lt;BR /&gt;You didn't mention whether or not you are using Online JFS.  This potentially could save you if you have it, but would make any significant change impossible without at least a umount of the FS.  Another suggestion, even as a temporary until you can get downtime, why not add a SAN LUN to your vg00 of say 30-50GB?  Then you can simply increase your / filesystem (assuming that you're not stuck with allocation and/or contiguous space issues).  As far as change control goes, our site has implemented something we call "master standards" where for certain activities such as increasing a filesystem, we simply fill out the appropriate CR record and no approval is required.  You might want to set this up (it could take you some time at first, but it's worth it down the road!) as part of this operation- typically this applies to well documented procedures that are repeatable.&lt;BR /&gt;&lt;BR /&gt;As to shrinking lvol4, again, with Online JFS, you're in a much better place - do you have it?</description>
      <pubDate>Thu, 18 Mar 2010 16:01:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230649#M553209</guid>
      <dc:creator>Abbott Vascular</dc:creator>
      <dc:date>2010-03-18T16:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230650#M553210</link>
      <description>Ooops :) I forgot and signed in as my group ID, I have a personal one for assigning points and will reply below.  My ID is RC Park.&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 18 Mar 2010 16:02:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230650#M553210</guid>
      <dc:creator>Abbott Vascular</dc:creator>
      <dc:date>2010-03-18T16:02:42Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230651#M553211</link>
      <description>Hi, I replied as Abbott Vascular, but if you assign points, please put them here. &lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 18 Mar 2010 16:09:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230651#M553211</guid>
      <dc:creator>RC Park</dc:creator>
      <dc:date>2010-03-18T16:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230652#M553212</link>
      <description>Hi Tom,&lt;BR /&gt;&lt;BR /&gt;Abbott Vascular/RC park, makes a good comment, without onlineJFS, the procedure cant be done "online", because the "to be extended" root filesystem, cant be unmounted once the system is booted.&lt;BR /&gt;&lt;BR /&gt;Greetz,&lt;BR /&gt;Chris&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Fri, 19 Mar 2010 10:17:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230652#M553212</guid>
      <dc:creator>chris huys_4</dc:creator>
      <dc:date>2010-03-19T10:17:37Z</dc:date>
    </item>
    <item>
      <title>Re: Expanding root file system</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230653#M553213</link>
      <description>It worked!  &lt;BR /&gt;&lt;BR /&gt;/tmp was mirrored to SAN disk, and then removed from local disk.  That freed up extents right next to /.  Next / was expanded on to the free space and finally /tmp was moved back to local disk.</description>
      <pubDate>Mon, 22 Mar 2010 12:58:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/expanding-root-file-system/m-p/5230653#M553213</guid>
      <dc:creator>Tom Ward_1</dc:creator>
      <dc:date>2010-03-22T12:58:34Z</dc:date>
    </item>
  </channel>
</rss>

