Description of problem: NFS server is RHEL with GFS, exporting to Solaris NFS client. 'cp' command on client causes permission denied error, destination file is created with 0 byte length. This error does not occur on RHEL clients NFS mounting the same GFS filesystem. The problem affects all user except root. We can: - move / copy files on a NFS-exported ext3 filesystem if he is on a RHEL NFS client as any non-root user - move / copy files on a NFS-exported ext3 filesystem if he is on a RHEL NFS client as the user "root" - move / copy files on a NFS-exported ext3 filesystem if he is on a Solaris NFS client as any non-root user - move / copy files on a NFS-exported ext3 filesystem if he is on a Solaris NFS client as any non-root user - move / copy files on the NFS-exported GFS-filesystem if he is on a RHEL NFS client as any non-root user - move / copy files on the NFS-exported GFS-filesystem if he is on a RHEL NFS client as the user "root" - move / copy files on the NFS-exported GFS-filesystem if he is on a Solaris NFS client as the user "root" If the non-root user logs into the NFS server he can move /copy files. The user CAN NOT: - move / copy files on the NFS-exported GFS-filesystem if he is on a Solaris NFS client as any non-root user Something we tried: mounted the remote filesystem from the Solaris client with: mount -F nfs san1:/u1/public /gfs Mount took. cd to user directory with permissions: drwxrwsr-x 2 sconnors 3864 Sep 1 17:01 ./ File "junk" is permissioned for the user (sconnors) 444 Attempted to copy a 444 (permissions) file as root and checked: 22 hurricane # cp junk junk10 23 hurricane # ls -la junk10 -r--r--r-- 1 root 10 Sep 1 17:01 junk10 Attempted to copy a 444 (permissions) file as sconnors and checked: sconnors@hurricane{46}cp junk junk20 cp: cannot create junk20: Permission denied Exit 2 Version-Release number of selected component (if applicable): rh-gfs-en-6.0-4 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
wonder if the setgid bit is confusing/complicating things.
This is a very old bugzilla that could be very much out of date. For now: (a) If Solaris client runs NFS v2/v3, I see no problem at all during cthon06. (b) If Solaris client is running NFS v4, NFS does have some cleaning up to do. If the original case is (a), I would like to close this as "being fixed". If the original case is (b), we need to transfer this bugzilla to NFS team. After nfs v4 clean up work is completed, we'll check to see how GFS works.
This is a very old bug and we could no longer get the customer contact info. Also if this is on NFS v2/v3, it works fine. Will close this as insufficient info.