Hmm, we do need to make that SEGFAULT not happen… Directories will be missing in life…

Get a tcpdump and look at where the handle that is causing the stale handle error is coming from. Do we handle map the handles shared in READDIR?

We also need to figure out why READDIRPLUS isn’t working…

Frank

From: Nick Couchman [mailto:nick.e.couchman@gmail.com]
Sent: Monday, June 28, 2021 12:04 PM
To: Solomon Boulos <boulos@google.com>
Cc: Todd Pfaff <pfaff@rhpcs.mcmaster.ca>; support@lists.nfs-ganesha.org
Subject: [NFS-Ganesha-Support] Re: Proxy FSAL - NFS4 -> 3

I'm sure I'm missing something simple, here, but still not sure why this is causing a segfault, unless the presence of the mutex lock/unlock does something to mess with it?

Well, I'm feeling a bit silly about this right now, and have resolved the segfault/core dump issue. The issue was that the directory for handle mapping didn't exist, so the HandleMap_Init function call would exit out without actually allocating the structures for digest and handle pools, but the proxy module would continue to try loading and try to use the handle map. Apparently I didn't catch this in the log file :-/.

That said, I'm on to the next issue, which is that, with handle mapping enabled, finally, and the nordirplus mount option (to get around the readdirplus issue), I now get a "Stale File Handle" error when trying to mount:

# mount -t nfs -o vers=3,nordirplus 10.1.2.4:/azure-file /mnt/azure

mount.nfs: Stale file handle

Current log file, during the mount attempt, is here:

https://pastebin.com/wKhLENFk

-Nick