After upgrading to 2.6.5 (from 2.6.3-r2), LVM2 volumes are no longer mountable. Same kernel config etc, even tried recompiling lvm2 with the new kernel. lvm lvs gives a correct output: LV VG Attr LSize Origin Snap% Move Move% local vg00 -wn--- 10.00G However, /dev/vg00/local points to the non-existant /dev/mapper/vg00-local (only /dev/mapper/control is there), so I think this is a bug in devfs. Also, there are dmessages like: devfs_mk_dir: invalid argument.<4>devfs_mk_dev: could not append to parent for / disc PS. Same problem with 2.6.4-r1 Reproducible: Always Steps to Reproduce:
Hi, you might try to update lvm2 and device-mapper to the ~x86-versions, lvm2-2.00.15 and device-mapper-1.00.17. After doing that i was again able to use my lv's. Just my 2
Hi, you might try to update lvm2 and device-mapper to the ~x86-versions, lvm2-2.00.15 and device-mapper-1.00.17. After doing that i was again able to use my lv's. Just my 2 ¢ents of ? PS1: Arch: x86, AMDk6-2@450 PS2: my original problem: vgscan segfaulted
Wow. This solved the problem. Many thanks!
User solved it. Excellent job.
It would be nice to make later kernels (>= 2.6.4) depend on the new versions of devmapper/lvm2.
New lvm2 is still marked as ~amd64. See e.g. http://bugs.gentoo.org/show_bug.cgi?id=59738.
Max, could you please look into getting this marked stable on the relevant arch's.
also between 2.6.8.1 and 2.6.9-mm1 there are incompatibilities (not only with lvm but also for samba and iproutes2)
*** Bug 59738 has been marked as a duplicate of this bug. ***
All the ebuilds required for this to work are already marked stable. If this is still an issue, re-open the bug.
