- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Expanding root file system
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2010 08:29 AM
03-17-2010 08:29 AM
/ is very small
/tmp is very large, and now spread across both local disks.
There are three disks in the vg00
c0t6d0 a 73GB local disk,
c6t6d0 a 73GB local disk, and
c64t5d3 a 8GB SAN LUN.
/dev/dsk/c0t6d0
--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol1 19 19
/dev/vg00/lvol2 256 256
/dev/vg00/lvol3 13 13
/dev/vg00/lvol4 13 13
/dev/vg00/lvol5 192 192
/dev/vg00/lvol6 384 384
/dev/vg00/lvol7 201 201
/dev/vg00/lvol8 576 576
/dev/vg00/lvol9 1952 1952
/dev/vg00/lvol10 768 768
/dev/dsk/c6t6d0
--- Distribution of physical volume ---
LV Name LE of LV PE for LV
/dev/vg00/lvol4 487 487
/dev/vg00/lvol9 288 288
bdf |grep vg00
/dev/vg00/lvol3 212992 190976 21928 90% /
/dev/vg00/lvol1 298928 45568 223464 17% /stand
/dev/vg00/lvol8 9437184 6426824 2989392 68% /var
/dev/vg00/lvol7 3293184 2554392 733048 78% /usr
/dev/vg00/lvol9 36700160 29003552 7604144 79% /u01
/dev/vg00/lvol4 8192000 313488 7817152 4% /tmp
/dev/vg00/lvol6 6291456 4188488 2086576 67% /opt
/dev/vg00/lvol5 3145728 2341184 804544 74% /home
My plan is to copy /u01 to a new SAN LUN and get it out of vg00.
Then mirror /tmp (lvol4) to c64t5d3. I was going to break the mirror and then mirror it back to c0t6d0.
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2010 08:34 AM
03-17-2010 08:34 AM
SolutionI 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.
However, I have to think that just doing an Ignite make_tap_recovery and rebuilding from that might be easier in the long run.
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2010 08:49 AM
03-17-2010 08:49 AM
Re: Expanding root file system
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2010 09:30 AM
03-17-2010 09:30 AM
Re: Expanding root file system
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.
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.
Changing file systems vg's, I think someone would notice.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-17-2010 10:15 AM
03-17-2010 10:15 AM
Re: Expanding root file system
I wouldn't take a chance doing something like this without an approved change request to cover things.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2010 09:01 AM
03-18-2010 09:01 AM
Re: Expanding root file system
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.
As to shrinking lvol4, again, with Online JFS, you're in a much better place - do you have it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2010 09:02 AM
03-18-2010 09:02 AM
Re: Expanding root file system
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2010 09:09 AM
03-18-2010 09:09 AM
Re: Expanding root file system
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2010 03:17 AM
03-19-2010 03:17 AM
Re: Expanding root file system
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.
Greetz,
Chris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2010 05:58 AM
03-22-2010 05:58 AM
Re: Expanding root file system
/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.