From: Vladimir Volovich <vvv@vsu.ru>
To: linux-kernel@vger.kernel.org
Subject: nfs - duplicate directory entries
Date: Fri, 10 Aug 2007 23:21:15 +0400 [thread overview]
Message-ID: <87fy2rgpqs.fsf@vvv.vsu.ru> (raw)
Hi!
we have an NFS server (windows-based), and mount a directory from this
server on a linux box; there is some bug appearing sometimes, namely
some of the directory entries are reported twice:
$ ls | wc
5968 5968 41776
$ ls | uniq | wc
5964 5964 41748
$ ls | uniq -d
112920
112921
112922
112923
$ ls -li | grep '11292[0123]'
8507232 drwx------ 2 web web 64 2007-02-09 10:54 112920
8507232 drwx------ 2 web web 64 2007-02-09 10:54 112920
8507219 drwx------ 2 web web 64 2007-02-09 10:54 112921
8507219 drwx------ 2 web web 64 2007-02-09 10:54 112921
8507195 drwx------ 2 web web 64 2007-02-09 10:54 112922
8507195 drwx------ 2 web web 64 2007-02-09 10:54 112922
8507188 drwx------ 2 web web 64 2007-02-09 10:54 112923
8507188 drwx------ 2 web web 64 2007-02-09 10:54 112923
i.e. the current directory contains sub-directory 112920 twice,
sub-directory 112921 twice, etc. - and the inode numbers are the same.
i wonder if you have ever seen such strange behavior? sometimes this
behavior is cured by unmounting and remounting the directory; but it
occurs regularly and reliably.
this does not happen if the directory from the same NFS server is
mounted on FreeBSD box.
linux version is 2.6.22 (from debian "sid").
the following information may of may not be related to the above bug:
the nfs server always reports link count for any directory as 2,
regardless of the number of subdirectories. (so e.g. find(1) says one
should use the -noleaf option).
if you need me to provide more information, please let me know.
Best,
v.
next reply other threads:[~2007-08-10 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 19:21 Vladimir Volovich [this message]
2007-08-10 20:42 ` nfs - duplicate directory entries Trond Myklebust
2007-08-10 21:05 ` Vladimir Volovich
2007-08-10 21:20 ` 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=87fy2rgpqs.fsf@vvv.vsu.ru \
--to=vvv@vsu.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.