- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Strict allocation policy problem
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
тАО06-28-2006 03:42 AM
тАО06-28-2006 03:42 AM
sbapc1:/#: lvextend -m 1 /dev/vg00/lvol8 /dev/dsk/c0t4d0
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg00/lvol8" could not be extended.
Failure possibly caused by strict allocation policy
<10 Points>
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 03:48 AM
тАО06-28-2006 03:48 AM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 03:50 AM
тАО06-28-2006 03:50 AM
Re: Strict allocation policy problem
Please post the output of vgdisplay -v vg00.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 04:13 AM
тАО06-28-2006 04:13 AM
Re: Strict allocation policy problem
>> Has the original been created with the strict allocation policy?
Can you tell what you are doing ? Is the volume lvol8 already mirrored ? [ lvdisplay -v /dev/vg00/lvol8 | grep -i mirror ]
The message indicates that disk having at least one of the mirror copy does not have enough free blocks. But mu question is if you already have a mirror what are you trying to do with the command you have posted ?
Regards,
Ninad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 04:14 AM
тАО06-28-2006 04:14 AM
Re: Strict allocation policy problem
I assume that the disks are identical.
It's not wise do disable strict allocation policy.
Can you check with vgdisplay -v vg00 and lvdisplay -v /dev/vg00/
Darrel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 04:18 AM
тАО06-28-2006 04:18 AM
Re: Strict allocation policy problem
Mirroring is useless when you mirror the content to the same drive.
The purpose of mirroring is to not lose data or system availability when a single disk fails.
If a logical volume called lvol3 (usually root) is on disk /dev/dsk/c0t0d0 and you make a mirror copy on /dev/dsk/c0t0d0 you have essentially wasted the disk space and not improved reliablity at all.
vgdisplay /dev/vg00
perhaps
vgdisplay -v /dev/vg00
Come up with a plan to redo all of your mirroing so that the logical volume you mirror ends up with the mirror copy on a different disk, perferably a different controller, eg c1 versus c0
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
тАО06-28-2006 06:08 AM
тАО06-28-2006 06:08 AM
Re: Strict allocation policy problem
logical volume in question is location on 2
different PVs. Even though I have enough
physical extents, I cannot mirror it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 01:22 PM
тАО06-28-2006 01:22 PM
Re: Strict allocation policy problem
does the lvdisplay show the allocation policy as PVG-strict/strict.
Then just give the
# lvextend -m 1 /dev/vg00/lvol8
LVM will ensure that the mirroring is proper.
else post the lvdisplay /dev/vg00/lvol8
regards
Albert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2006 06:59 PM
тАО06-28-2006 06:59 PM
Re: Strict allocation policy problem
What i did a while ago is the following;
- break mirrors to free a disk
- use pvmove to copy LE to the free disk till you have the extends free you need for extending lvol8 (in your case)
- extend lvol8
- use pvmove to copy the LE back to the first PV in the VG
[ optional: create PVG ]
- recreate the mirrors