Summary: | vgscan segfaults during boot w kernel 2.6.8-gentoo-r7 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lindsay Haisley <fmouse-gentoo> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lindsay Haisley
2004-10-12 20:57:11 UTC
I'm also running into a segfault if I set lvm.conf to scan /dev/md. I'm using devfs on this box, and have a RAID1 mirror set up, /dev/md0 -> /dev/md/0. I want to use this RAID array as an LVM physical volume, and can set it up, include it in a volume group and can create a workable logical volume in it; however, if I set up lvm.conf with the following: device { scan = "/dev/md" } and then run any of the lvm2 utilities, I get a segmentation fault. In particular, pvscan should pick up on the fact that /dev/md/0 has been set up as a LVM physical volume. Once this happens, there appears to be some sort of corruption somewhere, since if I remove the 'scan' line from lvm.conf subsequent invocation of most lvm2 utilities just hang indefinitely, and a reboot hangs on shutting down the Logical Volume Manager requiring that I use a hardware reset on the box. Relevant information on exactly this problem can be found at: <http://www.tgharold.com/techblog/2004/06/gentoo-segmentation-fault-in-vgscan.shtml> This looks like a interaction between devfs, md and lvm2 that needs to be addessed at a kernel level. The solution posted at <http://www.tgharold.com/techblog/2004/06/gentoo-segmentation-fault-in-vgscan.shtml> puts a band-aid on the problem here, too, although it doesn't appear to address the fundamental issue of what looks like adverse interactions between md, devfs and lvm2. At least _I_ can move on :-) If the information on the TechBlog (URL cited above) is accurate, this bug is basically another manifestation of the problem behind Bug #61258. |