- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- lvreduce error (lvm_lock)
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
05-13-2009 10:25 PM
05-13-2009 10:25 PM
lvreduce error (lvm_lock)
When i try to reduce the mirror we get the below error.
Cannot lock "/etc/lvmconf//lvm_lock" still trying ................
Details are as below.
$ ls -lt /etc/lvmconf/lvm_lock
---------- 1 root root 0 Jan 16 2003 /etc/lvmconf/lvm_lock
There are currently 2 lvreduce commands and one lvextend command running on server which are in hang state as shown below.
$ ps -eaf|grep -i lv|more
root 16041 15666 0 00:12:00 pts/17 0:00 lvreduce -m 0 /dev/vg00/lvol6 /dev/dsk/c1t0d0
root 14957 1 0 23:47:13 pts/tb 0:00 lvextend -m 2 /dev/vg00/lvol6 /dev/dsk/c2t0d0
root 18027 17522 0 00:58:06 pts/tc 0:00 lvreduce -m 1 /dev/vg00/lvol6 /dev/dsk/c2t0d0
Please help us resolve this issue.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:01 PM
05-13-2009 11:01 PM
Re: lvreduce error (lvm_lock)
that's normal, if you are working with LV* commands they are access /etc/lvmtab, lvm_lock is there for security reasons, that inform other app that, some command is changing the lvmtab.
Only one application in the same time can change LVMTAB.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:11 PM
05-13-2009 11:11 PM
Re: lvreduce error (lvm_lock)
u are running more than one LVM commands running. thats why u are facing such an error, please terminate other lvm commands and run one buy one.
thanks and regards
Sajjad Sahir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:19 PM
05-13-2009 11:19 PM
Re: lvreduce error (lvm_lock)
All the LVM commands have been terminated. Now we get the below error.
lvreduce -m 1 /dev/vg00/lvol6 /dev/dsk/c2t0d0
lvreduce: Couldn't reduce the logical volume:
Device busy
lvreduce: The LVM device driver failed to reduce mirrors on
the logical volume "/dev/vg00/lvol6".
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:27 PM
05-13-2009 11:27 PM
Re: lvreduce error (lvm_lock)
lvreduce could be use also with the -k switch.
But i will wait some time, end try again to reduce the mirror.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:34 PM
05-13-2009 11:34 PM
Re: lvreduce error (lvm_lock)
is the three-way mirror is still present ? Check the number of mirror copies with lvdisplay.
J.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:38 PM
05-13-2009 11:38 PM
Re: lvreduce error (lvm_lock)
send us vgdisplay -v vg00 out put
I think only one mirroring
lvreduce -m 0 /dev/vg00/lvol6 /dev/dsk/c2t0d0
thanks and regards
Sajjad Sahir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:39 PM
05-13-2009 11:39 PM
Re: lvreduce error (lvm_lock)
The number of mirror copies are 2. The mirro copy which we are reducing are having stale PE and we get the below error as shown. How to resolve this issue.
lvreduce -k -m 1 /dev/vg00/lvol6 /dev/dsk/c2t0d0
Physical extents on remaining physical volumes are stale or
Remaining physical volumes are not responding.
lvreduce: The LVM device driver failed to reduce mirrors on
the logical volume "/dev/vg00/lvol6".
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:46 PM
05-13-2009 11:46 PM
Re: lvreduce error (lvm_lock)
could you check if the disk that you like to remove from LVOL6 is not NO_HW ???
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:51 PM
05-13-2009 11:51 PM
Re: lvreduce error (lvm_lock)
As said first try finding out the disk that is NOT responding.
Then use this one:
lvdisplay -v -k /dev/vg_name/lvolXX
- Look for the pvkey of affected disk...say it is 0
Then try :
lvreduce -m 1 -k 0 /dev/vg_name/lvolXX
You can also use
vgreduce -f vg_name <== if the disk is not responding, all stale extents
Regds,
R.K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:57 PM
05-13-2009 11:57 PM
Re: lvreduce error (lvm_lock)
Output of pvdisplay and the disk is CLAIMED.
pvdisplay /dev/dsk/c2t0d0
--- Physical volumes ---
PV Name /dev/dsk/c2t0d0
VG Name /dev/vg00
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 8
Total PE 4340
Free PE 3830
Allocated PE 510
Stale PE 510
IO Timeout (Seconds) default
Autoswitch On
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2009 11:57 PM
05-13-2009 11:57 PM
Re: lvreduce error (lvm_lock)
lvdisplay -k /dev/vg02/lvol6 and note the pvkey
and lvreduce -k
thanks and regards
Sajjad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 12:17 AM
05-14-2009 12:17 AM
Re: lvreduce error (lvm_lock)
one think, what about sync the VG and if its in mirror state, use the lvreduce command again.
vgsync /dev/vgxx
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:04 AM
05-14-2009 01:04 AM
Re: lvreduce error (lvm_lock)
Find below the lvdisplay -v -k output.
Please let me know what is the PV key.
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2 PV3 PE3 Status 3
00000 0 01624 current 2 01624 stale 1 00000 stale
00001 0 01625 current 2 01625 stale 1 00001 stale
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:10 AM
05-14-2009 01:10 AM
Re: lvreduce error (lvm_lock)
Are 1 & 2 the PV key for the stale PE's as posted above.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:12 AM
05-14-2009 01:12 AM
Re: lvreduce error (lvm_lock)
pvkey 2 and 1 are stale
00001 0 01625 current 2 01625 stale 1 00001 stale
lvreduce -m 1 -k 1 /dev/vg_name/lvolXX
lvreduce -m 0 -k 2 /dev/vg_name/lvolXX
Or try:
vgreduce -f vg_name <<== to remove unavailable/unresponding disks from VG
Regds,
R.K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:42 AM
05-14-2009 01:42 AM
Re: lvreduce error (lvm_lock)
I get the following error when issued the command with K 1.
lvreduce -m 1 -k 1 /dev/vg00/lvol6
lvreduce: "1": No such file or directory
Usage: lvreduce
[-A Autobackup]
[-k]
{-m MirrorCopies |
-l LogicalExtentsNumber |
-L LogicalVolumeSize}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:46 AM
05-14-2009 01:46 AM
Re: lvreduce error (lvm_lock)
Try this one:
lvreduce â k â m 1 /dev/vg_name/lvolXX 1
Regds,
R.K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 01:59 AM
05-14-2009 01:59 AM
Re: lvreduce error (lvm_lock)
Could you please paste the command again. I see control characters.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 02:00 AM
05-14-2009 02:00 AM
Re: lvreduce error (lvm_lock)
lvreduce -Â Â k -Â Â m 0 /dev/vg_name/lvolXX 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 02:03 AM
05-14-2009 02:03 AM
Re: lvreduce error (lvm_lock)
lvreduce -k -m 1 /dev/vgname/lvolXX 1
lvreduce -k -m 0 /dev/vgname/lvolXX 2
- R.K.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 02:05 AM
05-14-2009 02:05 AM
Re: lvreduce error (lvm_lock)
Still getting the device busy error.
lvreduce -k -m 1 /dev/vg00/lvol6 1
lvreduce: Couldn't reduce the logical volume:
Device busy
lvreduce: The LVM device driver failed to reduce mirrors on
the logical volume "/dev/vg00/lvol6".
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 02:10 AM
05-14-2009 02:10 AM
Re: lvreduce error (lvm_lock)
try vgsync before you reduce the mirrors.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2009 03:10 AM
05-14-2009 03:10 AM
Re: lvreduce error (lvm_lock)
>>Allocated PE 510
>>Stale PE 510
>>IO Timeout (Seconds) default
There are stale PE in your disk that is what you are getting error messages.
Suraj