- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: lvreduce couldn't reduce logical volume
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
тАО08-05-2004 05:03 AM
тАО08-05-2004 05:03 AM
lvreduce: couldn't reduce logical volume:
no such file or directory.
The file for the LV exists, the file for the disks exists.
And upon further investigation an lvdisplay -v on the volume returns about 5000 extents as valid and the remaining 32000 with PX_NOPV.
Any help would be appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:05 AM
тАО08-05-2004 05:05 AM
Re: lvreduce couldn't reduce logical volume
Please show the syntax you are using.
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
тАО08-05-2004 05:07 AM
тАО08-05-2004 05:07 AM
Re: lvreduce couldn't reduce logical volume
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:13 AM
тАО08-05-2004 05:13 AM
Re: lvreduce couldn't reduce logical volume
1. Check whether your LV has mirror copies. for e.g. it is /dev/vg00/lvol4
# lvdisplay /dev/vg00/lvol4 | grep Mirror | cut -d " " -f 17
If this returns 1 then it is mirrored and 0 not mirrored.
so it should be 1
2. lvreduce -m 0
This should work.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:26 AM
тАО08-05-2004 05:26 AM
Re: lvreduce couldn't reduce logical volume
# lvdisplay /dev/vg02/lvol1
return ?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:35 AM
тАО08-05-2004 05:35 AM
Re: lvreduce couldn't reduce logical volume
mirror copies 1
consistency recovery mwc
schedule parallel
lvsize(mbytes) 614000
current le 38375
allocated pe 76750
but when you do a -v, the first 5600 show up fine with the logical extent followed by the first disk then the physical on that disk and the mirrored disk and the physical on that disk. beginning after about 5600, the display shows the logical extent followed by PX_NOPV followed by 00000 then PX_NOPV and 0000.
All other things point to the disks being fine, I can access data on the entire disk etc.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:41 AM
тАО08-05-2004 05:41 AM
Re: lvreduce couldn't reduce logical volume
# lvreduce -m 0 /dev/vg02/lvol1
This always works for me... give it a try once.
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 05:44 AM
тАО08-05-2004 05:44 AM
Re: lvreduce couldn't reduce logical volume
did you try a dd on the mirror disk that lvdisplay shows as PX_NOPV ?
dd if=/dev/rdsk/c5t6d0 of=/dev/null bs=1024k
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 06:04 AM
тАО08-05-2004 06:04 AM
Re: lvreduce couldn't reduce logical volume
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2004 06:26 AM
тАО08-05-2004 06:26 AM
SolutionWarning: 04/07/13 - This Critical Warning has been issued by HP.
- PHKL_29979 introduced behavior hat affects logical volumes with greater than or equal to 65536 physical extents. Logical volumes with less than 65536 physical extents are not affected by this defect. Since the maximum number of logical extents in a logical volume is 65535, this problem can only occur in mirrored logical volumes where the number of physical extents can exceed this number. For example, a logical volume with no mirrors contains 40000 logical extents and 40000 physical extents. Once this logical volume is mirrored, it will contain 40000 logical extents and 80000 physical extents.
The problem is due to the LVM kernel interface returning an incomplete mapping of extents to LVM commands.
The commands affected include lvdisplay(1M),
lvextend(1M), lvreduce(1M), lvsplit(1M), lvmerge(1M), pvmove(1M), and others. The incomplete extent map can cause LVM commands to fail or return incorrect results.
This can also lead to data corruption, as mirrors may not be fully resynchronized after a system panic.
- Below are examples of how the problem manifests itself in the output and execution of some of the LVM commands.
# lvdisplay -v /dev/vg02/lvol1
--- Logical volumes ---
LV Name /dev/vg02/lvol1
...
Current LE 32768
Allocated PE 65536
...
--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c16t0d0 32768 65536
--- Logical extents ---
LE PV1 PE1 Status 1
PV2 PE2 Status 2
00000 /dev/dsk/c16t0d0 00000 current
/dev/dsk/c16t0d0 00000 current
00001 /dev/dsk/c16t0d0 00000 current
PX_NOPV 00000 current
00002 PX_NOPV 00000 current
PX_NOPV 00000 current
...
32767 PX_NOPV 00000 current
PX_NOPV 00000 current
- As patch PHKL_29979 and the superseding patches PHKL_30552 and PHKL_30622 address an important number of critical defect fixes, HP advises to not remove these patches. The superseding patch, PHKL_30697, that will correct this behavior, is expected to be available by late August.
Formatting of above text is probably screwwed up. See the HP patch database.