SCIENTIFIC-LINUX-USERS Archives

March 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Akemi Yagi <[log in to unmask]>
Reply To:
Akemi Yagi <[log in to unmask]>
Date:
Wed, 20 Mar 2013 05:55:13 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
On Wed, Mar 20, 2013 at 1:22 AM, Antonietta Donzella
<[log in to unmask]> wrote:
> Hi,
> I share directories on a Scientific linux cluster by using nfs tool.
> SLC6 kernel 2.6.32-279.22.1.el6.x86_64
> nfs-utils-1.2.3-26.el6.x86_64
>
> After a server-client shutdown, a disagreeable event occurred.
> By making ls list on a nfs client shared directory, duplicated entries for
> some files are shown.
> Other files and sub-directories are non visible. The problem is not present
> on the nfs server.
> The directory don't contain an enormous number of files:
>
> On the server:
> #ls |wc -l
> 330
> #du -s
> 8855740
>
> On the client:
> #ls |wc -l
> ls: reading directory .: Too many levels of symbolic links
> 120
> n.b. there are only two symbolic links and they are not changed after the
> shutdown; however, the problem is not cleared if I remove them. #du -s
> not responding
> #dmesg
> some entries:
> ...
> NFS: directory images/dp contains a readdir loop.Please contact your server
> vendor. The file: .. has duplicate cookie 683570819
> NFS: directory images/dp contains a readdir loop.Please contact your server
> vendor. The file: .. has duplicate cookie 683570819
> __ratelimit: 2 callbacks suppressed
> NFS: directory images/green contains a readdir loop.Please contact your
> server vendor. The file: 57.png has duplicate cookie 1694199390
> NFS: directory images/green contains a readdir loop.Please contact your
> server vendor. The file: 57.png has duplicate cookie 1694199390
> ...
>
> I've tried to boot the system with the older kernel-2.6.32-279.el6.x86_64,
> and with the new kernel 2.6.32-358.2.1.el6.x86_64 but the bug is not
> cleared. Any ideas?
>
> Many thanks in advance
> Antonietta

Looks like you are affected by a known bug. It is probably the same as this one:

http://bugs.centos.org/view.php?id=6241

If so, there is no fix at the moment unfortunately.

Akemi

ATOM RSS1 RSS2