[fuse-devel] RELEASEDIR and OPENDIR called before 2nd READDIR through NFSv4 access.

[松下悟 <sma...@fo...>]

Hello all,

I am facing a strange behavior of FUSE. Could you please give me any advice
about NFS exporting FUSE based file system?

RELEASEDIR and OPENDIR is called before the second READDIR, when I list a
directory that contains many files through the NFSv4.

When I list the directory locally, they are not called.

In the case of return first entry of the directory to the second READDIR,
NFS client recieve EIO.

Since the "off" argument of the second READDIR is not zero, if I return the
continuation entry will hang kernel.

Is there any way that you can somehow processed correctly?

I will attach the log file of this test case.

unique:  21 - 144  local access sequence
unique: 180 - 202  NFS access sequence

Thanks in advance.


*** Server Environment
 OS   : CentOS 6.6 (Kernel 2.6.32-504.1.3.el6.x86_64)
 Fuse : 2.9.3

 Implemented by Fuse low-level API (include implements of LOOKUP for "."
and "..",
 written on README.NFS)

 Fuse mount options
   -o allow_other -o default_permissions -o big_writes

 /etc/exports
   /mnt/fusetest *(rw,sync,fsid=0,no_root_squash,anonuid=99,anongid=99)

*** Client Environment
 OS : CentOS 6.5 (Kernel 2.6.32-431.1.2.0.1.el6.x86_64)

 NFS Mount Command
   mount -t nfs4 192.168.0.xxx:/ /mnt -o hard,intr