Message-ID: <3C939132.F11E3D66@collab.net>
Date: Sat, 16 Mar 2002 10:38:42 -0800
From: Andrew Ryan <andrewr@collab.net>
MIME-Version: 1.0
To: Tavis Barr <tb62@columbia.edu>
Subject: Re: [NFS] NFS-HOWTO
References: <1016245811.1540.14.camel@vaio>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Nice job on the FAQ. It's been helpful for us setting up our NFS clients.

In 7.10, "File Corruption When Using Multiple Clients", you state that "If a
file has been modified within one second of its previous modification and left
the same size, it will continue to generate the same inode number." I don't
understand this statement -- it seems to me that the inode number of a file
should not change when a file is modified. I can see the mtime changing, but
not the inode number.

Also, this bug is new to me -- it's not in the previous NFS HOWTO, and I think
it deserves a lot more explanation as to why it happens now and also some
ideas for workarounds, both in 2.5 (where it will presumably be solved the
right way) and before 2.5 (where perhaps there is a hack that could be
applied).

Finally, is this bug a client-side bug, or does it just affect people using
linux as an NFS server?


thanks,
andrew
p.s. It would be nice if you could get the Netapp folks to contribute a
section in the interop chapter.


Tavis Barr wrote:

> Attached is a draft of the latest NFS-HOWTO, in HTML format.  (Put it
> all in the same directory and go to index.html).  Comments welcome.
>
> Cheers,
> Tavis