8:39 a.m.
On 8/12/19 10:00 AM, Erik Jacobson wrote:
> Okay, could you get a FULL_DEBUG log of the issue happening and
post it?
I am happy to get you snips from the various points if that's
interesting - like when the NFS mount happens, when the overlay happens.
What I pasted below is the output in FULL_DBEUG for all components when
I issued the failing su command. First the output of the command, then
the log snip that came out at the time the command below failed. I ran
this from our "miniroot" environment, chroot'd in to the target root.
That takes out the complexity of systemd and a full bootup. 'erikj' is
an account I created in the image so it exists in the nfs underdir.
Would you like output from the same command working when 'overlay' is
not in the picture? I'm so grateful for your help. I'll try to learn
about this output but it's overwhelming to me at first glance. :)
su: failsh-4.2# su - erikj
Last login: Mon Aug 12 08:53:07 CDT 2019
su: warning: cannot change directory to /home/erikj: Operation not supported
su: failed to execute /bin/bash: Operation not supported
So, everything in that log snippet succeeded, except a lookup on /root,
which returned ENOENT. In particular, there's no attempt to access
/home or /home/erikj in that snippet. Can you look for the first
occurrence of erikj in the log, and send a snippet around that? You're
looking for a line like this, but with "erikj" instead of "mail":
12/08/2019 08:54:45 : epoch 5d516e01 : leader1 :
ganesha.nfsd-29407[svc_14] nfs3_lookup :NFS3 :DEBUG :REQUEST PROCESSING:
Calling nfs_Lookup handle: File Handle V3: Len=40
4300000a20c81d9f835a974ac8a16529d95910db73b6306d8b535a493c89ec7727316bc227000000
name: mail
Daniel