- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problem extending /stand with lvextend and extendf...
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
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
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
06-06-2014 05:37 AM - last edited on 06-08-2014 07:53 PM by Lisa198503
06-06-2014 05:37 AM - last edited on 06-08-2014 07:53 PM by Lisa198503
Problem extending /stand with lvextend and extendfs
I have been able to extend several lvol's on my K370. However, when I try to extend /stand (lvol1), I get this message:
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol1" could not be extended.
Failure possibly caused by contiguous allocation policy.
Failure possibly caused by strict allocation policy.
When I try it with:
/sbin/extendfs -F vxfs /dev/vg00/rlvol1 I get this message:
/dev/vg00/rlvol1 invalid super-block
I have verified that lvol1 (/stand) is unmounted in both these attempts.
Why will the system extend lvol 8, lvol7, and lvol5 using these commands but not extend lvol1?
What do these errors mean and how do I get the system to extend lvol1?
Also, when using the lvextend command and including the '4096' variable (or any other larger number), is this 4096 bytes, 4096 kilobytes, or 4096 megabytes?
Glenn
P.S. This thread has been moved from HP 9000 to HP-UX > LVM and VxVM. -HP Forum Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2014 08:16 PM
06-08-2014 08:16 PM
Re: Problem extending /stand with lvextend and extendfs
>when using the lvextend command and including the 4096 value
"man lvextend" is your friend.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2014 09:22 PM
06-08-2014 09:22 PM
Re: Problem extending /stand with lvextend and extendfs
Question -- Why do you think you need to extend /stand?
/stand, primary swap, and the / volumes (lvol1, lvol2 and lvol3) are all special in that they must ALL be contiguous in their allocaiton. What that means is that ALL parts of /stand (lvol1) must be together on disk, then swap (lvol2) and then / (lvol3). Basically there is no EASY way to extend /stand.
The least difficult way is to create an Ignite backup tape and restore your system from it. When restoring from the Ignite tape, you can extend your volumes as you see fit.
Ignite is a very good tool that you should get familiar with.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2014 09:25 PM
06-08-2014 09:25 PM
Re: Problem extending /stand with lvextend and extendfs
When using 'lvextend' are you using '-L' or '-l' (ie. upper case L or lower case L)? The upper case '-L' value is MB. The lower case 'l' value is in extents (so to get size you have to multiply the # of extents by the physical extent size that the VG was configured with).
The upper case '-L' is far easier to use, in my opinion.