From: "Metathronius Galabant" <m.galabant@googlemail.com>
To: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: NFS: double dentries in directory with 2.6.20
Date: Fri, 16 Mar 2007 13:59:05 +0100 [thread overview]
Message-ID: <1b270aae0703160559r794cc36ake0248d71569cb5b8@mail.gmail.com> (raw)
Hi,
today I experienced double directory entries from a NFS mounted dir,
e.g. the file "file1.ext" is listed *twice* in the output.
The following under a 2.6.20 NFS client; Server was 2.6.18.8, NFS over UDP.
Mountpoint was not superblock-shared because it was a unique mount.
ls output:
drwxr-xr-x 3 user grp 296 Mar 15 17:28 ./
drwxr-xr-x 3 user grp 296 Mar 15 17:28 ./
drwxr-xr-x 3 user grp 72 Mar 15 17:28 ../
drwxr-xr-x 3 user grp 72 Mar 15 17:28 ../
drwxr-xr-x 2 user grp 80 Mar 15 17:28 00001/
drwxr-xr-x 2 user grp 80 Mar 15 17:28 00001/
-rw-r--r-- 1 user grp 357 Mar 15 17:28 00001.patterns.pvset
-rw-r--r-- 1 user grp 2057 Mar 15 17:28 00001.proc.pbs
-rw-r--r-- 1 user grp 66 Mar 15 17:28 00001.proc.pbs.dep
-rw-r--r-- 1 user grp 23 Mar 15 17:28 00001.proc.pbs.id
-rw-r--r-- 1 user grp 0 Mar 15 17:28 00001.proc.pbs.queued
-rw-r--r-- 1 user grp 0 Mar 15 17:28 00001.proc.pbs.queued
-rw-r--r-- 1 user grp 784 Mar 15 17:28 00001.proc.pvset
strace for getdents():
getdents64(3, {{d_ino=14652528, d_off=1, d_type=DT_DIR, d_reclen=24,
d_name="."} {d_ino=14652526, d_off=2, d_type=DT_DIR, d_reclen=24,
d_name=".."} {d_ino=14654778, d_off=3, d_type=DT_DIR, d_reclen=32,
d_name="00001"} {d_ino=14656129, d_off=4, d_type=DT_REG, d_reclen=48,
d_name="00001.proc.pbs.queued"} {d_ino=14652528, d_off=5,
d_type=DT_DIR, d_reclen=24, d_name="."} {d_ino=14652526, d_off=6,
d_type=DT_DIR, d_reclen=24, d_name=".."} {d_ino=14654778, d_off=7,
d_type=DT_DIR, d_reclen=32, d_name="00001"} {d_ino=14656129, d_off=8,
d_type=DT_REG, d_reclen=48, d_name="00001.proc.pbs.queued"}
{d_ino=14656022, d_off=9, d_type=DT_REG, d_reclen=40,
d_name="00001.proc.pbs.id"} {d_ino=14654835, d_off=10, d_type=DT_REG,
d_reclen=40, d_name="00001.proc.pbs.dep"} {d_ino=14654838, d_off=11,
d_type=DT_REG, d_reclen=40, d_name="00001.proc.pvset"}
{d_ino=14654841, d_off=12, d_type=DT_REG, d_reclen=40,
d_name="00001.patterns.pvset"} {d_ino=14654832, d_off=13,
d_type=DT_REG, d_reclen=40, d_name="00001.proc.pbs"}}, 32768) = 456
Only umounting and remounting did cure the problem which hasn't
reappeared as of now. The problem seemed to be localized into one
directory.
ATM I don't know how to track that down or supply any more information.
Please include me on CC.
Cheers,
M
reply other threads:[~2007-03-16 12:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1b270aae0703160559r794cc36ake0248d71569cb5b8@mail.gmail.com \
--to=m.galabant@googlemail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®