From: Stuart Kendrick <skendric@fhcrc.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: ls stalls
Date: Thu, 17 May 2012 16:51:34 -0700 [thread overview]
Message-ID: <4FB58F06.3020106@fhcrc.org> (raw)
In-Reply-To: <A364E35B-CDE6-44D7-8D99-06EDB31666D7@oracle.com>
> The file must reside in the directory you are listing, and it should be very large. Typically dd'ing zeroes into a large file is a good way to starve non-writers.
Thanx Chuck. I can replicate the problem, I've learned a lot about
dirty_bytes/dirty_ratio and I'm on my way to resolving this.
--sk
next prev parent reply other threads:[~2012-05-17 23:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FB43655.5040907@fhcrc.org>
2012-05-16 23:34 ` ls stalls Stuart Kendrick
2012-05-16 23:41 ` Chuck Lever
2012-05-17 13:12 ` Stuart Kendrick
2012-05-17 13:46 ` Chuck Lever
2012-05-17 23:51 ` Stuart Kendrick [this message]
2012-05-29 13:07 ` Stuart Kendrick
2012-05-29 16:20 ` Chuck Lever
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=4FB58F06.3020106@fhcrc.org \
--to=skendric@fhcrc.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).