- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LVM question
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
07-24-2003 07:32 PM
07-24-2003 07:32 PM
SO what I did is lvextend lvol7 -l 81 /dev/vg00/lvol7.
What happened now is when I do a lvdisplay for lvol7, the current LE is now 81 but the allocated PE has also increased by 12 from 150 to 162.
Why is it that also the allocated PE was increased?
Should I have just extended the filesystem and not the lvol anymore as the allocated PE is more than sufficient? If I just extend the file system, then would the current LE have changed to 81?
Can I still lvreduce lvol7 to its original size without destroying all the original contents of lvol7.
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 07:35 PM
07-24-2003 07:35 PM
Re: LVM question
lvdisplay /dev/vg00/lvol7
You can reduce it if you haven't done extendfs, mounted it and added data. You might have trouble at that point.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 07:41 PM
07-24-2003 07:41 PM
SolutionWhen you extended to 81 extents, increased by 6, it also had to increase the mirror copy by 6 extents thus making the total increase 12 extents, or your new total of 162 extents.
If you do an 'lvdisplay /dev/vg00/lvol7' you should see a row that says "Mirror Copies" and that is probably 1.
You have done absolutely nothing wrong. LVM is behaving as it should so you don't have to worry about increasing the mirror copy separate from the primary copy.
Just do your fsadm command now (assuming you have Online JFS) to increase the space that is usable for the filesystem and you will be OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 07:44 PM
07-24-2003 07:44 PM
Re: LVM question
root@hquov01.rwp.com:/->lvdisplay /dev/vg00/lvol7
--- Logical volumes ---
LV Name /dev/vg00/lvol7
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 3072
Current LE 768
Allocated PE 1536
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
You will notice that the 'Allocated PE' is double the number of 'Current LE'. That is because of the 'Mirror copies' of 1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 07:51 PM
07-24-2003 07:51 PM
Re: LVM question
lvdisplay -v /dev/vg00/lvol7
Mirroing would explain this.
The command would prove it.
When you expand a mirrored lvol and don't specify the mirror location, lvm maintains the mirror.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 08:21 PM
07-24-2003 08:21 PM
Re: LVM question
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 08:37 PM
07-24-2003 08:37 PM
Re: LVM question
I'd like to compliment Michael and Patrick on their diagnostic skills. Top notch. You guys are the best.
Good night.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 09:13 PM
07-24-2003 09:13 PM
Re: LVM question
Yes I have a mirror and it never occurred to me that the allocated PE was for both primary and mirror copy.