Kevin Coffman a écrit :
On Thu, Sep 4, 2008 at 2:59 PM, J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote:
On Thu, Sep 04, 2008 at 08:53:09PM +0200, François Valenduc wrote:
It's my home directory, so it has normal permission for such a directory:
drwxrwsr-x 77 francois francois 4,0K sep 4 20:43 francois/
So everybody has permission to read that directory--OK, that shouldn't
be a problem.
I don't think there is someting strange with this. I start running out
of ideas to get it working. I have reenabled nfs4 (which I also tried)
and it give the same problem. In order to do that, I off course changed
the exports file like this;
/export/francois
ordi-francois(nohide,rw,root_squash,no_subtree_check,sec=sys:krb5)
Let's just pick nfsv3 and stick with it; both nfsv3 and nfsv4 should
work, and switching between the two just complicates the debugging.
What does your mount commandline look like?
Could you get a network trace? Just start
tcpdump -s0 -wtmp.pcap
then attempt the mount, then after it fails kill tcpdump and send me
tmp.pcap.
--b.
This may be a stupid question, but can you access the mount using
auth_sys? As I think I said before, it looks like the Kerberos part
is working. (Unless there are errors on the client side from
rpc.gssd.)
I finally found a solution to the problem. It seems that it's needed to
compile both NFS v3 and v4 server support to make kerberos support
working. I find that a bit strange, but with this kernel configuration,
it is working fine. I find that a bit strange since I export the
filesystem as NFS3.
Should we consider this as a bug ? I am running kernel 2.6.26.3.
Thanks a lot for your patience,
François
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
