Re: 2.6.22-rc4-mm1

[Greg KH <greg@kroah.com>]

On Thu, Jun 07, 2007 at 07:02:23PM +0200, Jiri Slaby wrote:
> It'Greg KH napsal(a):
> > On Thu, Jun 07, 2007 at 05:54:13PM +0200, Jiri Slaby wrote:
> >> Tejun Heo napsal(a):
> >>> Jiri Slaby wrote:
> >>>> Tejun Heo napsal(a):
> >>>>> Jiri Slaby wrote:
> >>>>>> Yes. Now I'm compiling -rc4-mm2.
> >>>>> It's probably caused by new sysfs slimdown patches and I'm pretty sure
> >>>>> -rc4-mm2 would fail the same way.  The offending one should be one of
> >>>>> the following patches.
> >>>> There's reverted gregkh-driver-block-device in -mm2. So I wanted to give it a
> >>>> try. Do you think it's pointless and that patch has no impact on the behaviour?
> >>> I'm not familiar with how lvm vgscan works and the patch does look like
> >>> it can affect that.  Please give a shot at -mm2.
> >> Yup, it works without any further patches. So it seems like
> >> gregkh-driver-block-device is the culprit?
> > 
> > Culprit for what kind of symptom?  Is CONFIG_SYSFS_DEPRECATED enabled?
> > If not, can you try that?
> 
> LVM (lvm whatever) writes can't initialize lock 1 and quits.
> 
> SYSFS_DEPRECATED solves the issue (-rc4-mm2 minus the revert + SYSFS_DEPRECATED).

Great, thanks for letting us know.

Kay, what userspace tool is involved here that is getting confused?

thanks,

greg k-h