Can you do mount -vvv to get some more info on the client? The ganesha side doesn't *seem* to be sad.

It's getting and handling NULL, MNT_NULL, MNT_MNT, lookup of /azure-file (lookup of the root filehandle), and then responding to an FSINFO request.

If the mount -vvv isn't revealing, we might need a wireshark dump of the NFS traffic. For v3 I usually do:

sudo tshark -J "mount,rpc,nfs,nlm,portmap" -O "mount,rpc,nfs,nlm,portmap"  host <IP>



On Mon, Jun 28, 2021 at 12:03 PM Nick Couchman <nick.e.couchman@gmail.com> wrote:

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