Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have an OpenSolaris server (snv_101b) serving files via NFS. Everything works fine when mounting the shares on ESXi or OS X, but when I mount from Linux (CentOS 5.2) everything is mounted as nobody:nobody with 755 permissions. This means that the user cannot make any changes. How do I mount the share correctly?

The directory was shared with:

# zfs set sharenfs=on /tank/share

And is mounted with:

# mount -t nfs4 server:/tank/share /mountpoint

share|improve this question
    
Can I ask what is driving the preference for NFSv4? –  jasonjwwilliams May 28 '09 at 19:51
    
Mainly because newer generally equals better. I'm not really very experienced with NFS. However, the same problem happens with nfs3. –  Harley May 28 '09 at 21:59
add comment

3 Answers

NFSv4 does user@DOMAIN lookups (not simple UID/GID enforcement like NFSv3) so you need to have the same authentication database (files, LDAP, whatever) on both systems. With v3 all you need is to have the same UID/GID as the file...not necessarily the same username. If you don't need any of the features of v4, I'd recommend going with v3 on Linux. Historically, Linux has had a pretty flaky v4 implementation.

share|improve this answer
add comment

What version of NFS are you running client-side? Has CentOS 5.2 gotten around to NFSv4? Many distros are supporting NFSv3.

share|improve this answer
    
Pretty sure it's at 4. I'm sure it'd complain otherwise. The same thing happens if I use "mount -t nfs" –  Harley May 26 '09 at 6:04
    
Initial support for NFSv4 was added with RHEL4/CentOS 4.x, although I wouldn't recommend using it. I had some stability issues with it. With RHEL5.x/CentOS 5.x NFSv4 is solid and works quite well. –  Christopher Cashell May 26 '09 at 15:33
    
Yep, I'm using CentOS 5.2, as described in the question. :) –  Harley May 26 '09 at 21:32
add comment

Be careful if running CentOS 5.2 or the RHEL equal on the client side. There is a kernel/nfs-utils bug that will cause the system to hang.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.