Bug 702753 - LVMError: lvactivate failed for lv_home: device-mapper: resume ioctl failed: Invalid argument Unable to resume vg_cloud-lv_home (253:1)
Summary: LVMError: lvactivate failed for lv_home: device-mapper: resume ioctl failed...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: i386
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:c90177aeb0508a0a2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-06 20:22 UTC by rsedwardian
Modified: 2012-12-28 22:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-07 18:51:32 UTC
Type: ---


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (155.04 KB, text/plain)
2011-05-06 20:22 UTC, rsedwardian
no flags Details
Attached traceback automatically from anaconda. (98.77 KB, text/plain)
2012-12-28 22:52 UTC, shaleek.rice
no flags Details

Description rsedwardian 2011-05-06 20:22:17 UTC
The following was filed automatically by anaconda:
anaconda 14.22 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicelibs/lvm.py", line 403, in lvactivate
    raise LVMError("lvactivate failed for %s: %s" % (lv_name, msg))
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devices.py", line 2375, in setup
    lvm.lvactivate(self.vg.name, self._name)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1535, in handleVgLvs
    lv_device.setup()
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 1920, in _setupLvs
    if self.handleVgLvs(device):
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 2009, in populate
    if self._setupLvs():
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 400, in reset
    self.devicetree.populate()
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 117, in storageInitialize
    storage.reset()
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 212, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 131, in gotoNext
    self.moveStep()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1278, in setScreen
    self.anaconda.dispatch.gotoNext()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1191, in nextClicked
    self.setScreen ()
LVMError: lvactivate failed for lv_home:   device-mapper: resume ioctl failed: Invalid argument
  Unable to resume vg_cloud-lv_home (253:1)

Comment 1 rsedwardian 2011-05-06 20:22:24 UTC
Created attachment 497452 [details]
Attached traceback automatically from anaconda.

Comment 2 Brian Lane 2011-05-06 22:55:28 UTC
How the heck did it end up with - free?

20:21:19,754 DEBUG storage: vg vg_cloud has -196032MB free

Comment 3 David Lehman 2011-05-06 23:29:56 UTC
It looks like someone has resized the sda2 partition from 476416 MB to 276395 MB outside of the installer. Your lvm configuration is probably corrupted as a result, since you basically yanked a bunch of lvm's storage out from under it.

Comment 4 David Lehman 2011-06-07 17:53:51 UTC
Can you confirm that sda2 was resized prior to running the install?

Comment 5 rsedwardian 2011-06-07 18:23:51 UTC
I don't recollect resizing the partition outside the installer. However, I did get a successful install with suse after this installation failed.

Comment 6 David Lehman 2011-06-07 18:51:32 UTC
Ok, well there's nothing I can do with the information provided.

In the logs you can plainly see that LVM believes your PV is something like 47GB, while it is actually only around 27GB.

Comment 7 shaleek.rice 2012-12-28 22:52:27 UTC
Created attachment 670001 [details]
Attached traceback automatically from anaconda.


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