- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: pvmove crashed
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-07-2010 03:53 AM
тАО04-07-2010 03:53 AM
I was moving a volume group from one physical volume to another using "pvmove" when I loose connection to the server. "pvmove" crashed and, when I try to restart I get the following error:
# pvmove /dev/dsk/c10t0d1 /dev/dsk/c15t0d2
pvmove: Not enough free physical extents available.
Logical volume "/dev/vg01/lvol4" could not be extended.
pvmove: Cannot find a free physical extent for logical extent 17125
of logical volume "/dev/vg01/lvol4".
Failure possibly caused by strict allocation policy
srv00406:/root
The logical volume "lvol4" is in "stale" status.
# lvdisplay /dev/vg01/lvol4
--- Logical volumes ---
LV Name /dev/vg01/lvol4
VG Name /dev/vg01
LV Permission read/write
LV Status available/stale
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 300000
Current LE 37500
Allocated PE 37501
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
Question,
Is it possible to recover the vg/lvol or do I need to recreate the volume group and restore the data.
(this was a test server so the data is not critical)
/leif
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2010 04:02 AM
тАО04-07-2010 04:02 AM
SolutionHave a look at this doc.
http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=KBRC00010642
Title: Panic Hang On EMC Disk Array; Attempt To Migrate With pvmove(1M)
Document ID: emr_na-c00934877-4
Regards,
Robert-Jan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2010 04:05 AM
тАО04-07-2010 04:05 AM
Re: pvmove crashed
check the pvdisplay on the source and the destination PV, them recreate the structure on the destination disk, and them try to use the pvmove command again.
if its a test server, you can any time restore the VG and the data as you mentioned.
mikap
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2010 06:45 AM
тАО04-08-2010 06:45 AM
Re: pvmove crashed
e.g. lvchange -m 0 /dev/vg01/lvol4
That seems to remove the stale extent and keep the good one.
Doing another lvdisplay will show the Current LE and Allocated LE being the same (e.g. 37500) and mirror copies 0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2010 03:48 PM
тАО04-08-2010 03:48 PM
Re: pvmove crashed
Thank you, the "lvreduce -m" seem to be the correct way to go. Unfourtunatly for me is that "lvreduce -m" need the Mirror UX product and we don't have Mirror UX installed. I have to find out if we still have any valid license for this product so I can get a codeword for installing.
Or I have to recreate the volume and restore from backup.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-08-2010 11:14 PM
тАО04-08-2010 11:14 PM
Re: pvmove crashed
just an advice: next time you do such critical operation on the machine, do it from the LAN console. This way you can eliminate the side-effects of a possible connection loss.
Or, the best would be to do the work in 'screen', this is a virtual terminal which you can detach while the processes inside are kept running. We do it like this every day, I think it's a best practice.
http://hpux.connect.org.uk/hppd/hpux/Sysadmin/screen-4.0.3/
Unix operates with beer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2010 04:18 AM
тАО04-09-2010 04:18 AM
Re: pvmove crashed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2010 12:41 AM
тАО04-11-2010 12:41 AM
Re: pvmove crashed
How do you have an LVM mirror copy if you don't have MirrorDisk/UX ?
# lvdisplay /dev/vg01/lvol4
--- Logical volumes ---
LV Name /dev/vg01/lvol4
VG Name /dev/vg01
LV Permission read/write
LV Status available/stale
Mirror copies 1
Unix operates with beer.