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:[EMAIL PROTECTED] > Sent: Wednesday, August 29, 2007 8:00 PM > To: Hua Zhong > Cc: 'Linux Kernel Mailing List'; [EMAIL PROTECTED]; 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 > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/