All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	bjschuma@netapp.com, torvalds@linux-foundation.org,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] NFS readdir change break fully cached nfs root
Date: Tue, 2 Nov 2010 22:15:58 +0100	[thread overview]
Message-ID: <20101102211558.GE2167@basil.fritz.box> (raw)
In-Reply-To: <1288731930.534.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>

On Tue, Nov 02, 2010 at 05:05:30PM -0400, Trond Myklebust wrote:
> On Tue, 2010-11-02 at 19:00 +0100, Andi Kleen wrote:
> > My NFS root test systems stopped booting with 2.6.37-rc1. It just
> > hangs after entering user space.
> > 
> > The NFS root setup uses a slightly fancy parameter setup to minimize 
> > network traffic:
> > 
> > nfsroot=10.23.204.1:/home/nfsroot/edwin,nocto,acregmin=86400,acregmax=86400,acdirmin=86400,acdirmax=86400 root=/dev/nfs
> > 
> > I bisected it down to this commit from Bryan.
> > 
> > Unfortunately it's not trivially revertable because that conflicts
> > with later patches.
> 
> Does the following patch help?

Yes that fixes it. Thanks. Test system boots again.
-Andi

WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	bjschuma@netapp.com, torvalds@linux-foundation.org,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [regression] NFS readdir change break fully cached nfs root
Date: Tue, 2 Nov 2010 22:15:58 +0100	[thread overview]
Message-ID: <20101102211558.GE2167@basil.fritz.box> (raw)
In-Reply-To: <1288731930.534.1.camel@heimdal.trondhjem.org>

On Tue, Nov 02, 2010 at 05:05:30PM -0400, Trond Myklebust wrote:
> On Tue, 2010-11-02 at 19:00 +0100, Andi Kleen wrote:
> > My NFS root test systems stopped booting with 2.6.37-rc1. It just
> > hangs after entering user space.
> > 
> > The NFS root setup uses a slightly fancy parameter setup to minimize 
> > network traffic:
> > 
> > nfsroot=10.23.204.1:/home/nfsroot/edwin,nocto,acregmin=86400,acregmax=86400,acdirmin=86400,acdirmax=86400 root=/dev/nfs
> > 
> > I bisected it down to this commit from Bryan.
> > 
> > Unfortunately it's not trivially revertable because that conflicts
> > with later patches.
> 
> Does the following patch help?

Yes that fixes it. Thanks. Test system boots again.
-Andi

  parent reply	other threads:[~2010-11-02 21:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 18:00 [regression] NFS readdir change break fully cached nfs root Andi Kleen
2010-11-02 21:05 ` Trond Myklebust
     [not found]   ` <1288731930.534.1.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-11-02 21:15     ` Andi Kleen [this message]
2010-11-02 21:15       ` Andi Kleen
2010-11-03  7:31   ` Benny Halevy
2010-11-03 16:24   ` Nick Bowler
2010-11-04 16:06     ` Trond Myklebust
2010-11-04 18:57       ` Nick Bowler
2010-11-11 19:08       ` Andi Kleen

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=20101102211558.GE2167@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.