LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	kay.sievers@vrfy.org, Greg KH <gregkh@suse.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Alexey Dobriyan <adobriyan@sw.ru>,
	dm-devel@redhat.com, "Zhang, Rui" <rui.zhang@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [dm-devel] Re: 2.6.25-rc regression: kernel panic on boot
Date: Wed, 5 Mar 2008 01:19:45 +0000	[thread overview]
Message-ID: <20080305011945.GP1788@agk.fab.redhat.com> (raw)
In-Reply-To: <20080304104312.457ba3a8.akpm@linux-foundation.org>

On Tue, Mar 04, 2008 at 10:43:12AM -0800, Andrew Morton wrote:
> Isn't the device-mapper kernel code capable of detecting the older userspace
> version and loudly warning about it?  That at least would prevent us from
> wasting lots of people's time like this.
 
It's not a device-mapper problem: It's between userspace LVM2 and kernel
sysfs.

LVM2 userspace expects a particular sysfs layout.  That layout got
changed without offering sufficient lead time (>6-9 months) for the
required userspace changes to propagate into the main versions of the
distros people use.

LVM2 userspace version 2.02.29 (released 5th December 2007) can handle
old and new layouts.  The patch was in the CVS head for a while before
that.  Earlier versions of LVM2 require CONFIG_SYSFS_DEPRECATED.  A
less-efficient workaround is to disable the use of sysfs in the LVM2
config: 'devices { sysfs_scan = 0 }'.

(I think the root cause of this mess was changing what
CONFIG_SYSFS_DEPRECATED did instead of adding a new setting that could
be enabled by default.)

Alasdair
-- 
agk@redhat.com

  parent reply	other threads:[~2008-03-05  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 23:25 Zhang, Rui
2008-03-03 22:42 ` Greg KH
2008-03-03 18:33   ` Zhang, Rui
2008-03-04 13:54   ` Ingo Molnar
2008-03-04 18:43     ` Andrew Morton
2008-03-04 19:33       ` Greg KH
2008-03-04 20:04         ` Linus Torvalds
2008-03-04 20:24           ` Greg KH
2008-03-05 13:25             ` Ingo Molnar
2008-03-05  1:19       ` Alasdair G Kergon [this message]
2008-03-05 10:16     ` Alexey Dobriyan
2008-03-05 13:29       ` Ingo Molnar
2008-03-05 15:37       ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080305011945.GP1788@agk.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=adobriyan@sw.ru \
    --cc=akpm@linux-foundation.org \
    --cc=dm-devel@redhat.com \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [dm-devel] Re: 2.6.25-rc regression: kernel panic on boot' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).