From: Nick Bowler <nbowler@elliptictech.com>
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: Wed, 3 Nov 2010 12:24:23 -0400 [thread overview]
Message-ID: <20101103162423.GA3797@elliptictech.com> (raw)
In-Reply-To: <1288731930.534.1.camel@heimdal.trondhjem.org>
On 2010-11-02 17:05 -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.
[...]
> Does the following patch help?
[...]
> NFS: Fix a couple of regressions in readdir.
I just ran into this issue with git today, where some operations locked
up permanently (seemed to be an infinite readdir loop as described
elsewhere in this thread).
I applied this patch, and it solves the lockups, but there's a new
problem: the directory list sometimes comes back _empty_!
Here's the test script I used:
#!/bin/sh -e
mkdir gittest
cd gittest
git init
for i in `seq 500`
do
printf 'Hello\nWorld!\n' > $i.txt
done
git add ./*.txt
git commit -m 'Initial Commit'
sed -i 1d ./*.txt
git stash
git stash pop
echo 'Directory listing:'
ls
the 'ls' at the end prints nothing when the directory actually contains
500 files. If we insert an 'ls' just before the 'git stash pop', that
one prints the full listing. Touching the directory afterwards makes
the listings work again.
The script works fine on 2.6.36.
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2010-11-03 16:24 UTC|newest]
Thread overview: 8+ 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
2010-11-03 7:31 ` Benny Halevy
2010-11-03 16:24 ` Nick Bowler [this message]
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=20101103162423.GA3797@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=Trond.Myklebust@netapp.com \
--cc=andi@firstfloor.org \
--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 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).