mmakc/nfs-ganesha — comment on commit 0efbdbc827493a02a58fa808b2471cf62a4c9834
File:  line 0
By mmakc:

On Fri, 2 Mar 2012 04:56:29 -0800, Philippe DENIEL wrote:

PD> What kind of options ?
NFS mount options - just -o vers=3,nolocks.
Ganesha configuration options - --with-fsal=XFS --enable-nlm

PD> I have use FSAL_XFS hundreds of times (it was my default FSAL to
PD> compile with at cthon because it runs easily on my laptop) and
PD> met no issue of that kind.

So did I until today. It was only after I've started to run mtq client
from ogata-nfs in a loop to investigate I've noticed that occasionally
I'd get a file handle with some "strange" bytes at its tail. This is
one of those "uninitialized memory read" things which work perfectly
fine and then one day it doesn't.

BTW, VFS FSAL has similar code like XFS did before this change and
it's which is similarly wrong. And LUSTRE has been converted to use
the right size.

PD> Did you configure the xfs file system in a specific way ?
Nothing fancy except that I run it on a loop file which is sparse and
large.

max