From: "Russell Miller" <duskglow@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: NFS directory listing hang on write.
Date: Tue, 2 Dec 2008 16:05:10 -0800 [thread overview]
Message-ID: <4eea36270812021605s58f27857pda48fa3c5542affa@mail.gmail.com> (raw)
Hi, all. We're having some NFS problems here that I don't understand.
The arguments are standard. wsize=32768,rsize=32768,tcp. Nothing
else out of the ordinary. Test case is easy too:
mount a filesystem.
cd into the directory.
create a 1G file and background the creation, so 1G is being written
into the directory.
Then, try to ls the directory.
The ls will hang, sometimes for a few seconds, sometimes for the
entire length of the write. This happens on every NFS server I've
tried, including an acopia, bluearc, onstor, and a generic linux box
running on the other end.
I have seen this behavior on multiple systems and using multiple
kernels. Starting with the latest centos 5.2 kernel, but I've also
reproduced it on the stock 2.6.27.7. I don't really understand what's
going on, but I think it has something to do with the attribute cache,
as setting actimeo=1 seems to have a positive effect. Setting it to
zero seems to have no effect.
It does not seem to be happening with centos 4.x kernels, which are
based on 2.6.9.
I have turned on nfs and rpc debugging, and it's not telling me
anything useful, which is what I would expect if the attribute cache
is borking somehow. I don't think there's any debugging for the cache
itself.
Can someone please give me an idea of how to proceed in debugging
this? I'm not a stranger to the kernel, but this is deeper in than
I've gone before, and I am frankly a little over my head here.
Thanks,
next reply other threads:[~2008-12-03 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 0:05 Russell Miller [this message]
2008-12-03 0:21 ` Trond Myklebust
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=4eea36270812021605s58f27857pda48fa3c5542affa@mail.gmail.com \
--to=duskglow@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®