Hello,

I cannot access my home directory on an OpenSolaris server from a Linux NFS 
client. This is how I shared the ZFS dataset (public subnet censored):

        zfs set sharenfs=sec=none,r...@2002:****:****:3::/64:10.84.54.0/26 
rpool/export/home/andrej

Output from share:

        -...@rpool/export  /export/home/andrej   
sec=none,r...@2002:****:****:3::/64:10.84.54.0/26   ""

In fact I have no idea what this means. If I share rpool, rpool/export, 
rpool/export/home, ..., does it make any difference?

On the Linux client, I mounted the share like this:

        mount -t nfs4 10.84.54.10:/ /mnt/helium -o rsize=32768,wsize=32768

The command succeeded. I could list /mnt/helium and /mnt/helium/export. 
However, something went wrong one level deeper:

        # ls -l /mnt/helium/export/home
        ls: cannot access /mnt/helium/export/home/andrej: Permission denied
        total 0
        ?????????? ? ? ? ?            ? andrej

What's wrong with this? Who denied the permission and why? I thought this could 
be a problem similar to the absence of no_root_squash. (BTW, how can one say 
'no_root_squlash' on OpenSolaris?) The standard stupid brute-force solution 
'chmod -R ugo+rX andrej' did not help. Still the same error.

I could mount /, /export and /export/home. But presumably, /export/home/andrej 
could not be mounted:

        # mount -t nfs4 10.84.54.10:/export/home/andrej /mnt/helium -o 
rsize=32768,wsize=32768
        mount.nfs4: access denied by server while mounting 
10.84.54.10:/export/home/andrej

I have no idea why access is denied. With ZFS, it's not clear what's mounted 
and whether I'm crossing file system boundaries or not...

(BTW, I have the same user name on both machines, but a different user ID. Is 
it possible to establish a mapping so that the unprivileged user on the client 
can access his directory on the server? Anyway, first of all I need to mount it 
*somehow*...)

Any piece of information would be very helpful. I'm just about to through both 
machines through the window. :-( Perhaps this bug is be due to the poor NFSv4 
implementation on Linux... But it's much more probable that I just 
misconfigured something. Any suggestions?

Andrej

_______________________________________________
nfs-discuss mailing list
[email protected]

Reply via email to