[SOLVED] NFS Permissions

GRS63 · 01-09-2012, 06:11 PM

I had a NFS server set up under Fedora 15 It serviced Three Linux machines on the network and with samba operating as well two windows machines. Backup to an external driver were done regularly. The other day the had drive started to fail in the server so a new one was installed and Fedora 16 installed. NFS was installed and set up along with Samba.

The backed up data only being transferred to the new hard drive in the same location with the same folder names etc as it was on the Fedora 15 machine.

Samba works well to the windows machines but NFS is only working in part.

On the Linux client machines the Server Folder mounts and one can see all the folder levels within the the head Server folder. One can also see all the data files at the lowest level of each sub folder but each data file can not be accessed. Each file is marked with a "X". Clearly I have a permissions problem but I can not see where it is.

I have removed the new drive from the server and fired up the old drive and looked at the permissions to compare them with the new drive. As far as I can see the permissions and the set up between the two drives are the same.
As far as I can see the firewall settings are the same and as far as Selinux is concerned in the machine with fedora 15 it was "enabled" and in the new system it is "disabled".

Any ideas please

GRS

kbp · 01-09-2012, 06:21 PM

What does /etc/exports look like ?

GRS63 · 01-10-2012, 04:33 AM

Exports is

/home/Server/Data 192.168.0.0/255/255/255/0(rw,sync)

Look at this this afternoon
Checking to see if I get conformation of NFS mount when I
[root@Server ~] showmount

I get a message "clnt_create: RPC: Port mapper failure - timed out]

Comparing the firewall settings on the old drive Fedora 15 (managed to get it going on another machine)with the new machine fedora 16
Everything is the same, Same trusted services NFS4 and Samba same "other ports"

However when I compare rpcinfo -p on each machine I see some differences.

on the new machine there is an entry;
100024 1 udp 56490 Status. on the Fedora 15 machine the port number is 662
on the new machine there is an entry;
100024 1 udp 47169 Status. This does not appear on the fedora 15 machine
on the new machine there is an entry;
100005 1 udp 20048 Mountd on the Fedora 15 machine the port number is 982
There are another 5 entries for mountd all showing the same port number 2048 on the fedora 16 machine and port 892 on the fedora 15 machine.

comparing /etc/sysconfig/nfs
fist the two files are different
In the fedora 16 version there is no RQUOTAD_PORT that I can see there is a RQUOTAD =/usr/sbin/rpc. In the Fedora 15 version there is a RQUOTAD_PORT=875
In fedora 15 I have
RQUOTAD_PORT=875
LOCKD_TCPPORT=32803
LOCKD_UDPPORT=32769
MOUNTD_PORT=892
STATD_PORT=662

On Fedora 16 I have
RQUOTAD_PORT can not find an entry for this port
LOCKD_TCPPORT=32803
LOCKD_UDPPORT=32769
MOUNTD_PORT=892
STATD_PORT=662
RDMA_PORT= 20049

I am not sure but there seems to me to be a discrepancy between the rPCinfo -p ports and the ports given in the /etc/systemconfig/nfs file on the fedora 16 system. Namely the MOUNTD ports rpcinfo -p gives the port as 20048 where as the port given in /etc/systemconfig/nfs is 892. There seems to be agreement between the port numbers on the Fedora 15 system when the same tow files are compared.

In addition there is an additional entry in the rpcinfo -p file for "status" on the Fedora 16 system compared to the Fedora 15 system.

does anyone know if the Fedora 16 system has some errors because I do know the Fedora 15 system worked fine but I can not get the new Fedora 16 nfs system to work. As far as I can tell both machines are set up exactly the same in all other respects host names, user names, pass words etc. The only difference I did see and have not looked into why but the user ID on the fedora 15 machine is 500 where as the used ID on the fedora 16 machine is 1000.

thanks

deep27ak · 01-10-2012, 06:01 AM

Hello GRS63,

As the problem appears your NFS is not getting mounted
You have mentioned that you are using an external drive for this purpose so make sure that it is properly mounted and you make a proper entry in fstab and update your fstab

Code:

#mount -a

on the server machine

Code:

#vi /etc/exports
/home/Server/Data 192.168.0.0/255/255/255/0(rw,sync)<--check the syntax as I have never used such syntax in my nfs server
/home/Server/Data 192.168.0.0/24(rw,no_root_squash,sync) <--try this one

Code:

#exportfs -a
to update the exports file

Code:

#service portmap restart
just to make sure it is running properly

Code:

#service nfs restart

Code:

#showmount <--on server machine

On client

Code:

#mount -t nfs serverip:/home/Server/Data  /local/dir

GRS63 · 01-10-2012, 04:25 PM

Thanks.

Changed the file /etc/exports to
/home/Server/Data 192.168.0.0/24(rw,no_root_squash,sync)

#exportfs -a
/home/Server/Data
192.168.0.0/255.255.255.0

#service portmap restart
I get the following message
redirecting to /bin/systemctl restart portmap.service
failed to issue method call: unit portmap.service fails to load:
No such file or directory: See system logs and systemctl status portmap.service for details

#service status portmap.service
Portmap service
Loaded error

Reason: no file or sub directory)
active: inactive(dead)

not sure where to look for the system logs and how to view them

on Client machine
mount -t nfs 192.168.0.X:/home/Server/data /mnt/dir

Then using nautilus /mnt/dir
I can see all the folders
Going into a folder I can see the files but they are all marked "X" and can not be opened on the client machine

Thanks

GRS63 · 01-10-2012, 10:34 PM

I thank you very much for your time.
The issue has been solved. I solved it by changing the permission for the "others" in the Permissions tab of the /home/Server/Data folder.

There were no permissions for the "other" I changed it to Create and Delete and checked the change all files and folders under this and now I can read and write to all the files.

Thanks again