The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Vladimir Volovich <vvv@vsu.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs - duplicate directory entries
Date: Fri, 10 Aug 2007 16:42:09 -0400	[thread overview]
Message-ID: <1186778529.6642.52.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <87fy2rgpqs.fsf@vvv.vsu.ru>

On Fri, 2007-08-10 at 23:21 +0400, Vladimir Volovich wrote:
> 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.

That can happen if the NFS server doesn't send unique cookies.

Trond


  reply	other threads:[~2007-08-10 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10 19:21 nfs - duplicate directory entries Vladimir Volovich
2007-08-10 20:42 ` Trond Myklebust [this message]
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=1186778529.6642.52.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vvv@vsu.ru \
    /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