LVM doesn't autodetect MD

Bug #14768 reported by David Saxton
8
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_detection = 0" to "md_component_detection = 1" in /etc/lvm/lvm.conf when
installing.

Revision history for this message
In , Patrick Caulfield (patrick-debian) wrote : Re: Bug#278180: lvm2: md_component_detection should default to 1 instead of 0

On Mon, Oct 25, 2004 at 08:03:48PM +1000, Andrew Meaden wrote:
> Package: lvm2
> Version: 2.00.24-2
> Severity: wishlist
>
>
> In the default /etc/lvm/lvm.conf file, md_component_detection is set to
> 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

Revision history for this message
David Saxton (david-ubuntu) wrote :

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_detection = 0" to "md_component_detection = 1" in /etc/lvm/lvm.conf when
installing.

Revision history for this message
In , Patrick Caulfield (patrick-debian) wrote : Re: lvm2: md_component_detection should default to 1 instead of 0

I am reliably informed by Alasdair that the md_component_detection is
considerably better than it was. In fact it now uses the same detection
algorithm that MD itself uses.

So I think this should be set back on by default now.
--

patrick

Revision history for this message
In , Bastian Blank (waldi) wrote : Bug#278180: fixed in lvm2 2.02.02-1

Source: lvm2
Source-Version: 2.02.02-1

We believe that the bug you reported is fixed in the latest version of
lvm2, which is due to be installed in the Debian FTP archive:

clvm_2.02.02-1_i386.deb
  to pool/main/l/lvm2/clvm_2.02.02-1_i386.deb
lvm2-udeb_2.02.02-1_i386.udeb
  to pool/main/l/lvm2/lvm2-udeb_2.02.02-1_i386.udeb
lvm2_2.02.02-1.diff.gz
  to pool/main/l/lvm2/lvm2_2.02.02-1.diff.gz
lvm2_2.02.02-1.dsc
  to pool/main/l/lvm2/lvm2_2.02.02-1.dsc
lvm2_2.02.02-1_i386.deb
  to pool/main/l/lvm2/lvm2_2.02.02-1_i386.deb
lvm2_2.02.02.orig.tar.gz
  to pool/main/l/lvm2/lvm2_2.02.02.orig.tar.gz

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Blank <email address hidden> (supplier of updated lvm2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 12 Feb 2006 13:00:23 +0100
Source: lvm2
Binary: clvm lvm2-udeb lvm2
Architecture: source i386
Version: 2.02.02-1
Distribution: unstable
Urgency: low
Maintainer: Debian LVM Team <email address hidden>
Changed-By: Bastian Blank <email address hidden>
Description:
 clvm - Cluster LVM Daemon for lvm2
 lvm2 - The Linux Logical Volume Manager
 lvm2-udeb - The Linux Logical Volume Manager (udeb)
Closes: 278180 351632
Changes:
 lvm2 (2.02.02-1) unstable; urgency=low
 .
   * New upstream version.
   * Enable md_component_detection. (closes: #278180)
   * Set device permissions.
   * Don't use O_DIRECT on armeb. (closes: #351632)
Files:
 f7211df1f0e8ea5d52c22300d4464a0c 767 admin optional lvm2_2.02.02-1.dsc
 e5dfc205aaf673fecb3c1c15164d718c 477665 admin optional lvm2_2.02.02.orig.tar.gz
 4d8ea03a5e267c6d4f5c3a5b9f48ac2f 19443 admin optional lvm2_2.02.02-1.diff.gz
 d150d749cd8610f7e585f2fcdfa793d9 297910 admin optional lvm2_2.02.02-1_i386.deb
 35591e534459f5d9bda4f307f30ff2fa 175844 debian-installer optional lvm2-udeb_2.02.02-1_i386.udeb
 806df2535fd03cf0f141b19a95a3cc85 177498 admin extra clvm_2.02.02-1_i386.deb
Package-Type: udeb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iEYEARECAAYFAkPvJIsACgkQLkAIIn9ODhGtigCfTziTxxR/fhmLt059CvqRkkvo
R1sAoOdCdoJHwvtH7fZ38uWxc+j4NVVJ
=JvVU
-----END PGP SIGNATURE-----

Revision history for this message
Stevie Beth Mhaol (kormat) wrote :

Gah, added the 'upstream' bug-watch by mistake, it should have been the distro one.

Changed in lvm2:
status: Unknown → Fix Released
status: Unknown → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Surely this is fixed in Ubuntu by now?

Changed in lvmcfg:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.