Writing / Locking problem with NFSv4
Subsystems (2)
Hi there
I'm facing a rather strange problem.
Quoted 1 line
From one client I can mount and access my NFSServer without any problems.
Writing and locking works with a non root user accout.
Quoted 1 line
From another client (in another subnet), with root everything works fine. If
I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct - at least what ls -la and the logfiles for idmapd shows.
I appreciate your input! Thanks!
Tim
Quoted 10 lines · Tim
Im facing a rather strange problem.
From one client I can mount and access my NFSServer without any problems. Writing and locking works with a non root user accout.
From another client (in another subnet), with root everything works fine. If I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct at least what ls -la and the logfiles for idmapd shows.
Which client and server? (Linux on both? Which versions?) Are you using kerberos? If not, are your uid's the same between client and server? What does your export file look like?
--b.
Quoted 11 lines · Tim
Quoted 10 lines
I’m facing a rather strange problem.
From one client I can mount and access my NFSServer without any problems. Writing and locking works with a non root user accout.
From another client (in another subnet), with root everything works fine. If I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct – at least what ls -la and the logfiles for idmapd shows.
Quoted 1 line
Which client and server? (Linux on both? Which versions?) Are you using kerberos? If not, are your uid's the same between client and server? What does your export file look like?
Client and Server are both RHEL 6.1. I am not using kerberos. And yes, the uid's are the same, also the gid is the same: 3000 for both. This is my export file:
/srv/nfs/ 10.1.4.32/255.255.255.224(rw,fsid=0,sync,no_subtree_check,no_root_squash) 10.1.0.9(rw,fsid=0,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/users 10.1.4.32/255.255.255.224(rw,fsid=1,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/tmp 10.1.4.32/255.255.255.224(rw,fsid=2,sync,no_subtree_check,no_root_squash)/srv/nfs/testdata 10.1.0.9(rw,fsid=10,sync,no_subtree_check,no_root_squash)
I tried to take tcpdumps as root and non root user: They look the same to me. However, I'm not so sure what I'm looking for...
Thanks!
Tim
Quoted 17 lines · Tim
Quoted 11 lines · Tim
Quoted 10 lines
I’m facing a rather strange problem.
From one client I can mount and access my NFSServer without any problems. Writing and locking works with a non root user accout.
From another client (in another subnet), with root everything works fine. If I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct – at least what ls -la and the logfiles for idmapd shows.Quoted 1 line
Which client and server? (Linux on both? Which versions?) Are you using kerberos? If not, are your uid's the same between client and server? What does your export file look like?
Client and Server are both RHEL 6.1. I am not using kerberos. And yes, the uid's are the same, also the gid is the same: 3000 for both. This is my export file:
Quoted 6 lines
/srv/nfs/10.1.4.32/255.255.255.224(rw,fsid=0,sync,no_subtree_check,no_root_squash) 10.1.0.9(rw,fsid=0,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/users10.1.4.32/255.255.255.224(rw,fsid=1,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/tmp10.1.4.32/255.255.255.224(rw,fsid=2,sync,no_subtree_check,no_root_squash)/srv/nfs/testdata10.1.0.9(rw,fsid=10,sync,no_subtree_check,no_root_squash)I tried to take tcpdumps as root and non root user: They look the same to me. However, I'm not so sure what I'm looking for...
Hm. Sounds possibly like
http://marc.info/?t=129183437900003&r=1&w=2
--b.
Quoted 23 lines · Tim
Quoted 22 lines · Tim
Quoted 11 lines
Quoted 10 lines
I’m facing a rather strange problem.
From one client I can mount and access my NFSServer without any problems. Writing and locking works with a non root user accout.
From another client (in another subnet), with root everything works fine. If I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct – at least what ls -la and the logfiles for idmapd shows.Quoted 1 line
Which client and server? (Linux on both? Which versions?) Are you using kerberos? If not, are your uid's the same between client and server? What does your export file look like?
Client and Server are both RHEL 6.1. I am not using kerberos. And yes, the uid's are the same, also the gid is the same: 3000 for both. This is my export file:
/srv/nfs/10.1.4.32/255.255.255.224(rw,fsid=0,sync,no_subtree_check,no_root_squash) 10.1.0.9(rw,fsid=0,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/users10.1.4.32/255.255.255.224(rw,fsid=1,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/tmp10.1.4.32/255.255.255.224(rw,fsid=2,sync,no_subtree_check,no_root_squash)/srv/nfs/testdata10.1.0.9(rw,fsid=10,sync,no_subtree_check,no_root_squash)
Quoted 5 lines
Quoted 1 line
I tried to take tcpdumps as root and non root user: They look the same to me. However, I'm not so sure what I'm looking for...
Hm. Sounds possibly like
http://marc.info/?t=129183437900003&r=1&w=2
I just found out the reason for this whole strange behaviour: The folder, where the device is mounted, must have the right owner and / or rights. That means, if I mount it to /srv/data on client side, the folder data must belong to the user 3000. I just checked: vim *.swp - files are deleted afterwards and even locking is working!
But thank you anyway, Bruce!
Tim
Quoted 23 lines · Tim
Quoted 23 lines · Tim
Quoted 22 lines · Tim
Quoted 11 lines
Quoted 10 lines
I’m facing a rather strange problem.
From one client I can mount and access my NFSServer without any problems. Writing and locking works with a non root user accout.
From another client (in another subnet), with root everything works fine. If I use another user, locking doesnt work and also when I create a file with vim, the *.swp file is not deleted afterwards. But reading works without problems.
Strange thing is user mapping seems to work correct – at least what ls -la and the logfiles for idmapd shows.Quoted 1 line
Which client and server? (Linux on both? Which versions?) Are you using kerberos? If not, are your uid's the same between client and server? What does your export file look like?
Client and Server are both RHEL 6.1. I am not using kerberos. And yes, the uid's are the same, also the gid is the same: 3000 for both. This is my export file:
/srv/nfs/10.1.4.32/255.255.255.224(rw,fsid=0,sync,no_subtree_check,no_root_squash) 10.1.0.9(rw,fsid=0,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/users10.1.4.32/255.255.255.224(rw,fsid=1,sync,no_subtree_check,no_root_squash)/srv/nfs/mail/tmp10.1.4.32/255.255.255.224(rw,fsid=2,sync,no_subtree_check,no_root_squash)/srv/nfs/testdata10.1.0.9(rw,fsid=10,sync,no_subtree_check,no_root_squash)
Quoted 8 lines
Quoted 5 lines
Quoted 1 line
I tried to take tcpdumps as root and non root user: They look the same to me. However, I'm not so sure what I'm looking for...
Hm. Sounds possibly like
http://marc.info/?t=129183437900003&r=1&w=2I just found out the reason for this whole strange behaviour: The folder, where the device is mounted, must have the right owner and / or rights. That means, if I mount it to
/srv/dataon client side, the folder data must belong to the user 3000. I just checked: vim *.swp - files are deleted afterwards and even locking is working!
OK, so you just didn't have write permissions to that directory? Makes sense.--b.
Quoted 4 lines
But thank you anyway, Bruce!
Tim