- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LVM - Increasing LV size and then deciding to redu...
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
12-04-2000 06:29 AM
12-04-2000 06:29 AM
I am very worried that if I simply reduce the LV back to it's original size that LVM in all it's wisdom might decide to remove 100 Mb from an area that has a filesystem on it rather than the 100 Mb I have just increased it by! Is there any guarantee that this won't happen, HP can't seem to guarantee it!!!!!!!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2000 06:37 AM
12-04-2000 06:37 AM
Re: LVM - Increasing LV size and then deciding to reduce it before you have done anything with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2000 06:42 AM
12-04-2000 06:42 AM
Re: LVM - Increasing LV size and then deciding to reduce it before you have done anything with it.
You may want to take the course of 'prudence' here and follow the procedures for reducing a logical volume to ensure no loss of data.
Backup your data first, then reduce the lvol and reset the f/s. Normally on a lvreduce you would have to recreate the filesystem (since the lvol would now be less then the f/s..). But here your 'unique'..you may simple need to do a extendfs to reset it to the lvol. -or- you may want to take the course of recreating it.
Last restore your data.
Just a thought,
rcw
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2000 06:44 AM
12-04-2000 06:44 AM
SolutionI presume that you are using JFS and have done an 'lvextend' but not the 'fsadm' to actually expand the filesystem. I would complete the process and then reduce the filesystem. You may need to quiesce the filesystem before you get fsadm to reduce it.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2000 06:45 AM
12-04-2000 06:45 AM
Re: LVM - Increasing LV size and then deciding to reduce it before you have done anything with it.
DO a backup os that filesystem and then reduce. check it with fsck... OK ..
No problem.
All bad, No problem ... , reduce lvol, do newfs and recover from backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2000 07:47 AM
12-04-2000 07:47 AM
Re: LVM - Increasing LV size and then deciding to reduce it before you have done anything with it.
It worked when I did ir BUT, I did a complete level 0
backup prior BECAUSE, it was the SAFE thing to do.