From: Bruce Guenter <bruce@untroubled.org>
To: linux-nfs@vger.kernel.org
Subject: Invisible file problem
Date: Tue, 22 Feb 2011 15:52:14 -0600 [thread overview]
Message-ID: <20110222215214.GA32537@untroubled.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
I have come on a situation where a file in a directory is not showing up
in any directory listings, yet is still accessible by direct access. It
shows up in listings on the server but not on the client. I did a
capture of the NFS protocol traffic, and the file is showing up in the
readdir call results. If I recreate the directory using the same file
names but empty files, the behavior persists.
I am running vanilla 2.6.37.1 on both client and server, using NFSv4.
The server filesystem is ext4.
Is this a kernel NFS client bug? Is there anything else I can do to
diagnose the source of the problem, or any way to work around it?
Thanks.
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-02-22 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:52 Bruce Guenter [this message]
2011-02-23 7:50 ` Invisible file problem Trond Myklebust
2011-02-23 14:50 ` Bruce Guenter
2011-02-23 19:42 ` Joe Landman
2011-02-23 20:23 ` Bruce Guenter
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=20110222215214.GA32537@untroubled.org \
--to=bruce@untroubled.org \
--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).