> *To:* Frank Filz
> *Cc:* NFS Ganesha Developers ;
> de...@lists.nfs-ganesha.org
> *Subject:* Re: [Nfs-ganesha-devel] FD reuse in NFSv3
>
>
>
> Ganesha 2.5.1 with my own FSAL.
>
>
>
> How do I subscribe to new listserve?
>
> --Satish
>
>
>
> On Mon
Ganesha Developers ;
de...@lists.nfs-ganesha.org
Subject: Re: [Nfs-ganesha-devel] FD reuse in NFSv3
Ganesha 2.5.1 with my own FSAL.
How do I subscribe to new listserve?
--Satish
On Mon, May 7, 2018 at 5:58 PM, Frank Filz mailto:ffilz...@mindspring.com> > wrote:
> My NFS cl
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.>> NFS client is a legacy implementation and it is not going to be fixed.
How is it going to work if there is a real network failure? In any case,
the behavior you are describing should never happen? Do
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.Ganesha 2.5.1 with my own FSAL.
How do I subscribe to new listserve?
--Satish
On Mon, May 7, 2018 at 5:58 PM, Frank Filz wrote:
> > My NFS client does not retry I/O.
> > Ganesha is reusing FD instead
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.
> My NFS client does not retry I/O.
> Ganesha is reusing FD instead of opening file for every read request.
> Sometimes it closes the fd even when there is a worker waiting still in
> read() call on the
