Amar,
Thx for answering us. Is there any other solutions with 3.2.X to avoid this
issue except restarting gluster daemon ?
And also, when 3.3.x will be in a stable version ?
Thx
Anthony
>Message: 1
>Date: Mon, 30 Apr 2012 21:44:50 +0530
>From: Amar Tumballi <amarts at redhat.com>
>Subject: Re: [Gluster-users] Gluster-users Digest, Vol 48, Issue 43
>To: Gerald Brandt <gbr at majentis.com>
>Cc: gluster-users at gluster.org, anthony garnier <sokar6012 at
hotmail.com>
>Message-ID: <4F9EBA7A.5080500 at redhat.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> You are having the exact same problem I am. So far, no response from
anyone at Gluster/RedHat as to what is happening or if this is a known issue.
>
>
>Hi Gerald/Anthony,
>
>This issue is not easy to handle with 3.2.x version of gluster's NFS
>server. This issue is being addressed with 3.3.x branch (ie current
>master branch). Please try 3.3.0beta3+ or qa36+ for testing the behavior.
>
>This happens because NFS process works on FH (file handles), and for
>that we needed to keep a fd-ref till NFS client has reference to filehandle.
>
>With 3.3.0, we changed some of the internal way how we handle NFS FHs,
>so this problem should not happen in 3.3.0 release.
>
>
>Regards,
>Amar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20120504/9d28c077/attachment.html>