LVM doesn't autodetect MD
Bug #14768 reported by
David Saxton
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 |
Fix Released
|
Unknown
|
|||
lvm2 (Debian) |
Fix Released
|
Unknown
|
|||
lvmcfg (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson |
Bug Description
Installer failed to succesfully create lvm file systems on a raid 5 device - the filesystems could not be mounted after
rebooting from the install cd.
This was fixed by changing the option "md_component_
installing.
Changed in lvm2: | |
status: | Unknown → Fix Released |
status: | Unknown → Fix Released |
To post a comment you must log in.
On Mon, Oct 25, 2004 at 08:03:48PM +1000, Andrew Meaden wrote: detection is set to
> Package: lvm2
> Version: 2.00.24-2
> Severity: wishlist
>
>
> In the default /etc/lvm/lvm.conf file, md_component_
> 0, which causes problems with md devices containing superblocks.
It's set to zero because it's unreliable, see several lvm2 bug reports that were
submitted about this that caused me to disable the option...
If you want to set it to 1 on your machine the feel free to do so, but I'm
afraid it's just too much trouble to be a default.
Sorry.
patrick