https://bugzilla.novell.com/show_bug.cgi?id=810408
https://bugzilla.novell.com/show_bug.cgi?id=810408#c2
James Carter changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|jimc@math.ucla.edu |
--- Comment #2 from James Carter 2013-03-28 04:51:15 UTC ---
I reverted the client's /etc/nfs.mount so Nfsvers is not set (default is 4).
On the server I did: echo N >
/sys/module/nfsd/parameters/nfs4_disable_idmapping (it formerly contained Y).
Then, as you predicted, the client got the files owned correctly.
(Wipes egg off face...) I have a file /etc/modprobe.d/55-nfs-mathnet.conf
which used to say:
options nfsd nfs4_disable_idmapping=y
However, on the test server I put in the kernel command line
"nfsd.nfs4_disable_idmapping=y". As a result, changing the value in
/etc/modprobe.d/55-nfs-mathnet.conf had no effect. (Checking: cat
/sys/module/nfsd/parameters/nfs4_disable_idmapping says Y.) I removed the
kernel parameter and changed to "options nfsd nfs4_disable_idmapping=0", and
rebooted the server (and for paranoia, the client).
Success!
ls -ld /net/tabbycat/m1/.
drwxr-xr-x 9 root root 4096 Mar 19 15:37 /net/tabbycat/m1/./
grep tabbycat /proc/mounts
tabbycat:/m1/ /net/tabbycat/m1 nfs4 rw,relatime,vers=4, etc.
So I think we have a complete resolution and the status could be changed to
"not a bug". Thank you for your help and sorry to bother you for my own
spaghetti tangle. However, I was expecting a true value of the parameter to
disable ID mapping.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.