From: Richard Mittendorfer <delist@gmx.net>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: "Xin Zhao" <uszhaoxin@gmail.com>
Subject: Re: NFS readdir problem
Date: Mon, 15 May 2006 18:18:41 +0200 [thread overview]
Message-ID: <20060515181841.27fc86de.delist@gmx.net> (raw)
In-Reply-To: <4ae3c140605150836i3f8d3890pa8568bf7d0431a7b@mail.gmail.com>
Also sprach "Xin Zhao" <uszhaoxin@gmail.com> (Mon, 15 May 2006 11:36:53
-0400):
> Hi,
Hello,
> I use NFS to read a remote directory, which contains 56 entries. But
> after the read, "ls -al" only show 26, 31, or 51 entries in three test
> runs.
>
> I have read the NFS code "encode_entry" and related "nfs_readdir",
> "nfs3_proc_readdir"..., but haven't find the right place that can
> cause this problem.
>
> Is there anyone has similar experience? Please help!
There is a note in the performance section from the NFS-HOWTO[1]. It
suggests adjusting the r- and wsize mount parameters:
_._. .._ _ .... . ._. . __..__ _._. .._ _ .... . ._. .
Directly after mounting with a larger size, cd into the mounted file
system and do things like ls, explore the filesystem a bit to make sure
everything is as it should. If the rsize/wsize is too large the
symptoms are very odd and not 100% obvious. A typical symptom is
incomplete file lists when doing ls, and no error messages, or reading
files failing mysteriously with no error messages. After establishing
that the given rsize/ wsize works you can do the speed tests again.
Different server platforms are likely to have different optimal sizes.
_._. .._ _ .... . ._. . __..__ _._. .._ _ .... . ._. .
[1] http://www.tldp.org
> Thanks,
> -x
sl ritch
next prev parent reply other threads:[~2006-05-15 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 15:36 Xin Zhao
2006-05-15 16:18 ` Richard Mittendorfer [this message]
2006-05-15 19:10 ` Matthew Wilcox
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=20060515181841.27fc86de.delist@gmx.net \
--to=delist@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.com \
/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®