- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: "LogicalExtentsNumber" is not bigger than curr...
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
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
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
тАО04-20-2004 03:25 AM
тАО04-20-2004 03:25 AM
"LogicalExtentsNumber" is not bigger than current setting
Any idea what's wrong?
The outputs of pvdisplay -v and lvdisplay are attached.
Thanks,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 03:30 AM
тАО04-20-2004 03:30 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
Thanks,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 03:30 AM
тАО04-20-2004 03:30 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 03:32 AM
тАО04-20-2004 03:32 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
In that command the LE # should be the new *total* # of LEs. So add old to new addition for the new total.
Rgds,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 03:32 AM
тАО04-20-2004 03:32 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
In general, the -L option is easier to use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 03:42 AM
тАО04-20-2004 03:42 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
check this thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=184562
Phelix explains very well that message.
Best regards,
Ettore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 04:29 AM
тАО04-20-2004 04:29 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
if you want to add 1gb by LE you need to add 256 (per your vgdisplay) to the logical volume
lvextend -l $((1800 + 256)) /dev/vgp08/lvol2
if you wanted to do it by MB
lvextend -L $((7200 + 1024)) /dev/vgp08/lvol2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 05:40 AM
тАО04-20-2004 05:40 AM
Re: "LogicalExtentsNumber" is not bigger than current setting
I was originally using sam to extend the lvol since it also automatically extends the file system associated with it (we're using Online JFS). I then tried from the command line and found that the source of the problem was that the file system's lost+found directory had been deleted (not by me), so the fsadm command was failing. By recreating it the directory, fsadm worked fine.
Thanks for the help,
Tim