Hello,
I seem to be hitting a corner case where ganesha (2.6-rc2) does not respond
to a RENEW request from 4.0 client. Enabled the debug logs and noticed that
NFS layer has not seen the RENEW request (I can see it in tcpdump).
I collected netstat output periodically and found that there is a
>From Daniel Gryniewicz :
Daniel Gryniewicz has uploaded this change for review. (
https://review.gerrithub.io/396237
Change subject: DRC - Clean up full cached compounds when session ends
..
DRC - Clean up
On Fri, Jan 19, 2018 at 06:03:55PM +, Sriram Patil wrote:
> Hi Neils,
>
> Thanks for confirming this. I can take care of moving posix_acls and
> changing glusterfs build scripts. I am not very sure about the CI
> though. It would be great if someone can help me out on that.
I think Jiffin or
Hmm, I need to check all the conditions, but it looks like someone has to do
something when the fsal_obj_handle passed up to mdcache is not actually
consumed. Probably mdcache needs to release the obj handle. I think mdcache may
need to call release on the obj handles it doesn't consume. In the
How about this as a band-aid, since non-chunked readdir is going away:
https://review.gerrithub.io/396194
Daniel
On 01/24/2018 05:29 AM, Kinglong Mee wrote:
With the latest codes (nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64),
set ganesha.conf includes,
CACHEINODE {
Dir_Max = 50;
>From Daniel Gryniewicz :
Daniel Gryniewicz has uploaded this change for review. (
https://review.gerrithub.io/396194
Change subject: MDCACHE - cache entry even if parent dir full
..
MDCACHE - cache entry
Hi,
I have been continuously seeing this issue when running pynfs test suite
WRT14st_write.testLargeWrite : RUNNING
Traceback (most recent call last):
File "/root/pynfs/nfs4.0/lib/testmod.py", line 222, in run
self.runtest(self, environment)
File