No subject

does not have inodes in the same way other filesystems do. It instead
has object ids which don't behave the same way (not as persistant?)
However the NFS daemon expects to be given inodes when referring to an
exported filesystem.

What appears to happen is a remote machine requests a file, NFS gets the
inode for the file and deals with it, the remote system requests the
same file again and NFS now uses it's cached inode expecting it to refer
to the same file in the filesystem, however with reiserfs it doesn't and
so the corruption.

There are patches for this being developed. But I haven't looked for
their current status in a while.

Most of this I gleaned off the reiserfs mailing list archive found on
www.reiserfs.org. Whether my interpretation is correct is another
matter...:)

Hope that helps,

Cheers

Kim

-- 
====================================================================== 
Kim Covil - CSIRO Exploration & Mining   E-mail: kimc at ned.dem.csiro.au
            PO Box 437, Nedlands,        Tel: +61 8 9284 8425   ,-_!\
            Western Australia  6009      Fax: +61 8 9389 1906  /     \
                                                               *_,-._/
=================================================================== v 
   Please direct all personal e-mail to kimbotha at covil.com.au