Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#1996 - LVM broken - device mapper can't load device

Attached to Project: Arch Linux
Opened by Sasha (kleptophobiac) - Saturday, 08 January 2005, 23:29 GMT
Last edited by Judd Vinet (judd) - Monday, 10 January 2005, 18:49 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

It is impossible to manage logical volumes after the 2.00.32 update. All lv* operations result in

device-mapper ioctl cmd 9 failed: Invalid argument

I have tried on a previously working system, and on a brand new installation.

Reverting to 2.00.25 makes lvm work like a charm on both the brand new and the old system.
This task depends upon

Closed by  Judd Vinet (judd)
Monday, 17 January 2005, 18:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  Problem magically went away. ;)
Comment by dorphell (dorphell) - Sunday, 09 January 2005, 00:22 GMT
Have you tried recompiling it?
Comment by Sasha (kleptophobiac) - Sunday, 09 January 2005, 00:51 GMT
Yes, using abs, but to no avail. I think there is something incompatible between the Arch stock kernel and the new LVM2.
Comment by Judd Vinet (judd) - Monday, 10 January 2005, 18:49 GMT
Does "lvm lvdisplay" also generate this error for you?
Comment by Sasha (kleptophobiac) - Thursday, 13 January 2005, 01:30 GMT
lvm lvdisplay using the new version results in an immediately suspended logical volume (accompanied by an extremely long HDD thrash and 100% CPU usage) and then similar errors.

Again, reverting to 2.00.25 works great.

I'll do some more experimenting with the new version this weekend when I have some extra free time.
Comment by Judd Vinet (judd) - Thursday, 13 January 2005, 05:23 GMT
Odd. It works fine for me on my raid/lvm box. Is there anything else notable about your system? Custom kernel, udev/devfs, etc?
Comment by Sasha (kleptophobiac) - Thursday, 13 January 2005, 21:30 GMT
Stock 2.6.10 kernel (didn't work with 2.6.9 either), stock packages, udev and devfs are equally bad with the new lvm. It happened with my homebrew file server, as well as a fresh out of the box Dell SC420 using packages downloaded that night.

I'm very perplexed, especially since you don't have the issue, but I've repeated the problem on two completely separate computers.

It doesn't bother me very much, as the current LVM2 doesn't offer me anything of value over the old LVM2 package... but it was unnerving to be unable to access my data for a while until I isolated the problem.
Comment by Judd Vinet (judd) - Saturday, 15 January 2005, 23:30 GMT
Hi Sasha,

2.00.33 just came out. Please let me know if this one works for you.
Comment by Sasha (kleptophobiac) - Monday, 17 January 2005, 17:25 GMT
Works fine!

Loading...