Ok, I see how that can happen.
The 2.4 stable branch has something that should be a workaround, set
CacheInode {
Dir_Max = 1;
}
In your config which disables dirent caching, that might workaround.
In the meantime I am working on a new dirent cache that will use the cookies
from the underlying filesystem, and if it doesn’t find the start cookie in the
cache, it will do an underlying readdir starting at that cookie, which will
either find a next dirent, or will be beyond the end of the directory and
indicate end of dir. It will also preserve the dirent order from the
underlying filesystem so all of this will work.
I hope to finish that next week, and if all goes well, it is slated for
backport to 2.4 stable.
Frank
From: Satish Chandra Kilaru [mailto:iam.kil...@gmail.com]
Sent: Friday, February 17, 2017 2:39 PM
To: nfs-ganesha-devel@lists.sourceforge.net
Subject: [Nfs-ganesha-devel] Ganesha (2.2.0-6.el7) returns bad cookie error
during readdir on NFSv4 share
I am using
My application does the following..
1) opendir
2) readdir(entry) (exit loop if error)
3) delete(entry)
4) go to step 1
After deleting all entries in the directory it exits from step 2 with error
code 523 (BADCOOKIE).
I verified this application with NFSGanesha and with other NFS servers.
Only Ganesha (2.2.0-6.el7) returns this error.
Has this been fixed in a recent version. If yes which version has this fix?
Thank you
-Satish
--
Please Donate to www.wikipedia.org <http://www.wikipedia.org>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
