2008-05-26 11:41:15

by Jeff Layton

[permalink] [raw]
Subject: Re: Nfs filesystem corruption(?) after kmail crash

On Mon, 26 May 2008 10:44:07 +0200
"Alexander Borghgraef" <[email protected]> wrote:

> On Fri, May 23, 2008 at 9:08 PM, Talpey, Thomas
> <[email protected]> wrote:
> >> The main thing here is that I'd like to understand why this is
> >>happening? What does it mean when ls returns something like:
> >>
> >>d????????? ? ? ? ? ? cur
> >
> > This is something very different. (I'm assuming this "ls" was done on the
> > NFS mount and not the server itself.)
> Yes, ls on the NFS mount on the client.

> > Usually, this happens because there
> > are no attributes available locally - ls seems to know only the filetype
> > (directory) and filename (cur). What client kernel version are you running?
> Client kernel:
> Server kernel: 2.6.9-1.667

The ???? fields usually pop up when stat() calls fail. The odd thing in
this case though is that stat() seemed to figure out that this was a
directory and not a plain file, but missed out on everything else.

Is this problem persistent? If so, it might be interesting to run:

strace stat cur

...and see what error it's returning. Even better would be to get a
capture on the wire at the same time and see if the server is returning
an error of some sort.

Jeff Layton <[email protected]>