From: "Hua Zhong" <hzhong@gmail.com>
To: 'Ian Kent' <raven@themaw.net>
Cc: 'Linux Kernel Mailing List' <linux-kernel@vger.kernel.org>,
autofs@linux.kernel.org, 'Adrian Bunk' <bunk@kernel.org>
Subject: RE: regression of autofs for current git?
Date: Wed, 29 Aug 2007 20:09:36 -0700 [thread overview]
Message-ID: <010401c7eab3$38d16100$aa742300$@com> (raw)
In-Reply-To: <1188442804.4090.10.camel@raven.themaw.net>
I am in the process of bisecting now. It takes a while but the bad commit is
between 2.6.22 and 13f9966b3ba5b45f47f2ea0eb0a90afceedfbb1f (June 28). I'll
continue tomorrow.
My system is FC4.
autofs-4.1.4-26
nfs-utils-1.0.7-13.FC4
By the way, the particular autofs commit Andrian sent is innocent. It's
something else.
It will still take me about 10 reboots to bisect. If anyone has a patch for
me to try, I'll give it a shot tomorrow.
> -----Original Message-----
> From: Ian Kent [mailto:raven@themaw.net]
> Sent: Wednesday, August 29, 2007 8:00 PM
> To: Hua Zhong
> Cc: 'Linux Kernel Mailing List'; autofs@linux.kernel.org; Adrian Bunk
> Subject: Re: regression of autofs for current git?
>
> On Thu, 2007-08-30 at 00:47 +0200, Adrian Bunk wrote:
> > On Wed, Aug 29, 2007 at 01:58:58PM -0700, Hua Zhong wrote:
> >
> > > Hi,
> >
> > Hi Hua,
> >
> > > I am wondering if this is a known issue, but I just built the
> current git
> > > and several autofs mounts mysteriously disappeared. Restarting
> autofs could
> > > fix some, but then lose others. 2.6.22 was fine.
> > >
> > > Is there anything I could check other than bisect? (It may take
> some time
> > > for me to get to it)
> >
> > the commit below is the only autofs4 patch that went into the git
> tree
> > since 2.6.22.
> >
> > Does reverting it fix your problems?
>
> Maybe but there is an NFS change that appears to be in the current
> 2.6.23-rc kernel and doesn't seem to be in 2.6.22 that is known to
> break
> some autofs maps and also breaks amd.
>
> I can't seem to locate the commit just now.
> In the meantime what version of user space autofs and nfs-utils are you
> running?
> And can you post your autofs maps please?
>
> Ian
>
>
WARNING: multiple messages have this Message-ID (diff)
From: "Hua Zhong" <hzhong@gmail.com>
To: "'Ian Kent'" <raven@themaw.net>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
<autofs@linux.kernel.org>, "'Adrian Bunk'" <bunk@kernel.org>
Subject: RE: regression of autofs for current git?
Date: Wed, 29 Aug 2007 20:09:36 -0700 [thread overview]
Message-ID: <010401c7eab3$38d16100$aa742300$@com> (raw)
In-Reply-To: <1188442804.4090.10.camel@raven.themaw.net>
I am in the process of bisecting now. It takes a while but the bad commit is
between 2.6.22 and 13f9966b3ba5b45f47f2ea0eb0a90afceedfbb1f (June 28). I'll
continue tomorrow.
My system is FC4.
autofs-4.1.4-26
nfs-utils-1.0.7-13.FC4
By the way, the particular autofs commit Andrian sent is innocent. It's
something else.
It will still take me about 10 reboots to bisect. If anyone has a patch for
me to try, I'll give it a shot tomorrow.
> -----Original Message-----
> From: Ian Kent [mailto:raven@themaw.net]
> Sent: Wednesday, August 29, 2007 8:00 PM
> To: Hua Zhong
> Cc: 'Linux Kernel Mailing List'; autofs@linux.kernel.org; Adrian Bunk
> Subject: Re: regression of autofs for current git?
>
> On Thu, 2007-08-30 at 00:47 +0200, Adrian Bunk wrote:
> > On Wed, Aug 29, 2007 at 01:58:58PM -0700, Hua Zhong wrote:
> >
> > > Hi,
> >
> > Hi Hua,
> >
> > > I am wondering if this is a known issue, but I just built the
> current git
> > > and several autofs mounts mysteriously disappeared. Restarting
> autofs could
> > > fix some, but then lose others. 2.6.22 was fine.
> > >
> > > Is there anything I could check other than bisect? (It may take
> some time
> > > for me to get to it)
> >
> > the commit below is the only autofs4 patch that went into the git
> tree
> > since 2.6.22.
> >
> > Does reverting it fix your problems?
>
> Maybe but there is an NFS change that appears to be in the current
> 2.6.23-rc kernel and doesn't seem to be in 2.6.22 that is known to
> break
> some autofs maps and also breaks amd.
>
> I can't seem to locate the commit just now.
> In the meantime what version of user space autofs and nfs-utils are you
> running?
> And can you post your autofs maps please?
>
> Ian
>
>
next prev parent reply other threads:[~2007-08-30 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 20:58 regression of autofs for current git? Hua Zhong
2007-08-29 22:47 ` Adrian Bunk
2007-08-30 3:00 ` Ian Kent
2007-08-30 3:09 ` Hua Zhong [this message]
2007-08-30 3:09 ` Hua Zhong
2007-08-30 3:25 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2007-08-30 9:49 Martin Knoblauch
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='010401c7eab3$38d16100$aa742300$@com' \
--to=hzhong@gmail.com \
--cc=autofs@linux.kernel.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.