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
Opened by Sasha (kleptophobiac) - Saturday, 08 January 2005, 23:29 GMT
Last edited by Judd Vinet (judd) - Monday, 10 January 2005, 18:49 GMT
|
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. ;)
Monday, 17 January 2005, 18:15 GMT
Reason for closing: Fixed
Additional comments about closing: Problem magically went away. ;)
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.
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.
2.00.33 just came out. Please let me know if this one works for you.