2008-05-23 19:09:14

by Talpey, Thomas

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

At 10:44 AM 5/23/2008, Alexander Borghgraef wrote:
> Is ext3 known for time resolution issues? Switching to a different fs
>could prove problematic, but I could always ask the sysadmin to move
>my home dir to my client machine, there should be enough space so that
>would rule out any synchronization problems.

Yes, ext3's timestamps resolve to (only) one second. Use the stat(1)
command to see them. They cause problems for NFS, which depends
on them for its consistency checks. Other filesystems and servers do
not have this issue.

> 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.) 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?