Ganesha not working with Amd Automounter
Hi all, Has anyone used Ganesha with Amd Automounter? One of our customers used Ganesha 2.7 with it and saying they saw intermittent issues like hangs, permission denied or EIO errors. Restart of Ganesha seems to fix the issue. But it again happens after sometime. The tcpdump that was provided seems to show multiple v3 NFS NULL requests. There are no failures/errors seen as such. GETPORT to portmapper on NFS server for program 10005 version 3 (MOUNT v3) is not being seen in it and neither is the actual MOUNT request being seen. Looks like there are messages from amd eg- "/etc/maps/global.map mounted fstype auto ..." and it leads to LOOKUP's. But immediately after that amd starts reporting messages like- "file server XXXXX, type nfs, state not responding" They also mentioned that Amd worked fine with Ganesha 2.5. Any insights on what change between the two versions can cause to break this, would be really useful for us to know. Thanks and regards, Trishali. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Trishali Nayar IBM Systems ETZ, Pune. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I've never used any automounter with Ganesha, so I have no personal experience here. A lot changed between 2.5 and 2.7 (and between 2.7 and 3), so there's nothing I could point to directly. Logs might be helpful. Or, if it can be managed, before and after tcpdump output, so we can see what changed. Daniel On 10/27/20 8:08 AM, Trishali Nayar wrote:
Hi all,
Has anyone used Ganesha with Amd Automounter?
One of our customers used Ganesha 2.7 with it and saying they saw intermittent issues like hangs, permission denied or EIO errors. Restart of Ganesha seems to fix the issue. But it again happens after sometime.
The tcpdump that was provided seems to show multiple v3 NFS NULL requests. There are no failures/errors seen as such. GETPORT to portmapper on NFS server for program 10005 version 3 (MOUNT v3) is not being seen in it and neither is the actual MOUNT request being seen.
Looks like there are messages from amd eg- "/etc/maps/global.map mounted fstype auto ..." and it leads to LOOKUP's. But immediately after that amd starts reporting messages like- "file server XXXXX, type nfs, state not responding"
They also mentioned that Amd worked fine with Ganesha 2.5. Any insights on what change between the two versions can cause to break this, would be really useful for us to know.
Thanks and regards, Trishali.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Trishali Nayar IBM Systems ETZ, Pune. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________ Devel mailing list -- devel@lists.nfs-ganesha.org To unsubscribe send an email to devel-leave@lists.nfs-ganesha.org
participants (2)
-
Daniel Gryniewicz -
Trishali Nayar