This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours
Bug 598037 - pvmove fails after a while
pvmove fails after a while
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: lvm2 (Show other bugs)
13
x86_64 Linux
low Severity high
: ---
: ---
Assigned To: LVM and device-mapper development team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-31 05:56 EDT by Rabie van der Merwe
Modified: 2010-05-31 10:43 EDT (History)
11 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-31 10:43:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Rabie van der Merwe 2010-05-31 05:56:26 EDT
Description of problem:
While attempting a pvmove of my Fedora 13 install from one disk to another it will stop after an variable amount of time with 2 error messages:
udevd[438]: worker [766] unexpectedly returned with status 0x0100
udevd[438]: worker [766] failed while handeling '/devices/virtual/block/dm-1'

I still have console activity (I can press enter and get lines to move up on screen in single user mode) or when I was doing it from a cmdline in X I could spawn more consoles but not perform any activity in them.

Version-Release number of selected component (if applicable):
kernel-2.6.33.4-95.fc13.x86_64
udev-151-9.fc13.x86_64
lvm2-2.02.61-1.fc13.x86_64

How reproducible:
So far everytime, once the machine crashes I would reboot and run pvmove to restart the move.

Steps to Reproduce:
1.pvmove /dev/sda2 /dev/sdb2
2.wait for it to fail after completing a portion of the move
3.
  
Actual results:
pvmove fails after a period of time, which require a beboot and restart of pvmove

Expected results:
pvmove completes after 100% without error messages

Additional info:
Comment 1 Rabie van der Merwe 2010-05-31 06:02:07 EDT
I also just noticed on some LVM commands I get the following output onscreen:
File descriptor 9 (pipe:[110831]) leaked on lvcreate invocation. Parent PID 870: /bin/bash
Comment 2 Rabie van der Merwe 2010-05-31 10:43:23 EDT
For some reason I now cant replicate the issue after the original pvmove completed in the end.

Note You need to log in before you can comment on or make changes to this bug.