unable to mount the NFS entries

English Network/Internet
1

Hey there, I been searching google and forums for about 5 hours now, and can’t figure this one out, I have a server running opensuse 11.2 sharing various NFS directories, I have one laptop that is running 11.2 and I have no problem getting my NFS shares from the server.

On my other laptop that is running 11.3, I had the shares working at one point, but changed things around and added a new HD to the server, now I can NOT get this thing to work, I have tried everything I could find to read on it.

Started and stopped the NFS server and exportfs -a, and checked /var/logs/messages on server and nothing about this laptop (192.168.0.102 suse 11.3) trying to connect.

On this laptop, I have deleted all the shares, and tried to re-add them but still get this error everytime.

on server /etc/export:

/home/kryptic/ *(rw,no_subtree_check,sync)
/backup/Media/ *(rw,no_subtree_check,sync)
/backup/Dales_Backup/ *(fsid=0,crossmnt,ro,root_squash,sync,no_subtree_check)
/backup/Tashas_Backup/ *(ro,root_squash,sync,no_subtree_check)
/home/tasha/ *(ro,root_squash,sync,no_subtree_check)

On laptop that won’t work, /etc/fstab:

/dev/disk/by-id/ata-Hitachi_HTS722080K9A300_071003DP0B00DQG8MJGA-part5 swap swap defaults 0 0
/dev/disk/by-id/ata-Hitachi_HTS722080K9A300_071003DP0B00DQG8MJGA-part6 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-Hitachi_HTS722080K9A300_071003DP0B00DQG8MJGA-part7 /home ext4 acl,user_xattr 1 2
/dev/disk/by-id/ata-Hitachi_HTS722080K9A300_071003DP0B00DQG8MJGA-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=en_US.UTF-8 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
192.168.0.100:/home/tasha /home/tasha/Network_Folder nfs defaults,gid=Backup,insecure 0 0

tried adding gid and insecure, read that somewhere, usually I have default,auto,tcp,intr,ro or rw in there.

on the laptop that works (11.2) my /etc/fstab is (quick eg, don’t wanna type all that’s in there):

192.168.0.100:/home/kryptic /home/kryptic/Network_Folder nfs defaults,auto,tcp,rw,intr 0 0

…

rpcinfo -p show’s only portmapper running, not status or nlockmgr, and I have nfs-common installed.

help lol

2

Hi,

just a short idea:
192.168.0.100:/home/kryptic /home/kryptic/Network_Folder nfs defaults,auto,tcp,rw,intr 0 0
192.168.0.100:/home/tasha /home/tasha/Network_Folder nfs defaults,gid=Backup,insecure 0 0

are very different i think.

/home/kryptic/ *(rw,no_subtree_check,sync)
/home/tasha/ *(ro,root_squash,sync,no_subtree_check)

and this too.

So what about just changing the tasha folder to the same as kryptic and take a look if it works?

3

You say “but still get this error everytime.”, but I do not see any error message in your post. Please post the output of

mount -a

(and please, please, use CODE tags around computer text by using the # button in the toolbar and when there is no # button use the “Go advanced” button below first).

Also, did you use YaST > Network services > NFS clinet to configure? Or did you different?

BTW changing the mountpoint as johest suggested is of no use (on the assumption that both mount points exist). One can mount file systems (NFS or otherwise) to onea liking.

4

Why not?
different mount points on different machines with different options and one of it works… so what?
So changing the one which does not work to the same option the other, working, mount point has should work.
If not we definetly have an nfs problem.

5

Sorry, error message was the title of the thread, I was using yast2 and NFS Client config when I set it all up and hit finish all it would give me is:

Unable to mount the NFS entries from /etc/fstab

Tash-NiX:/home/tasha # mount -a
mount.nfs: access denied by server while mounting 192.168.0.100:/home/tasha

I’m not sure why I would be getting that error, like I said, I had this working before, I just changed a few things.

I will use the # button, now, I rarely post in forums, usually just read and read… this one has me stumped tho.
Thanks

6

Johest, the tasha directory was exactly the same as the kryptic directory, I have just been changing things around trying out everything I have read, I can’t get any of my NFS shares to work on this 11.3 laptop.

7

I guessed that more or less, but I like real computer output copied and pasted.

And we see now that YaST only gave a general conclusion: “Does not work”, while the CLI gives us more information. Can you reverse those changes and of course first try if it works, so we know it is realy due to the changes. And when it works, add the changes one by one until you got stuck?

BTW you could save your /etc/fstab first, so you have a fallback. Also in this case, I would do that testing by editing /etc/fstab and not via YaST. After all while YaST is pretty good at doing a lot of things, in principle it is an extra layer that can introduce errors.

Anomter thing that comes to mind is of course how to interprete “access denied”. That should lead to checking all routers in between and all personal firewalls on both systems.

No hard feelings, but when nobody tells you we all have to suffer from the malformed output. And as the new version of the forums software hasn’t the # button in the Quick reply it is even harder to tell people. Sigh!

8

I only changed two things and that was a media directory and a backup directory, the ‘tasha’ directory remained unchanged, and the reason for the directory change was new HD, router and firewalls were all configured, everything else worked fine, ftp, ssh, ping.

So some how I landed up on another thread about how NFS hangs on boot, and a user named dochm suggested “Edit /etc/nfsmount.conf as root and find the line with #Defaultvers=4, remove the # and change 4 to 3.”

And now it works…

Bug? or something I did?

Thank you for your help

9

Earlier I had the idea asking you about if you use version 3 or 4, but because you said you had it running and did not change there, I dropped it.

In YaST > Network Services > NFS client there is a check about version 4. Maybe you clicked that by accident.

In any case, nice it works now and thanks for reporting back. This might be of use to others.

10

No the check isn’t selected in the NFS Client, I did try it with and without at one point, because nothing was working.

How does the computer identify itself over NFS? I have this question now, I have 2 directories set up on the backup hard drive one dales_backup (owner kryptic group backup) the other tasha_backup (owner tasha group backup) I set both of them up with 700 permissions, on my laptop 11.2 (username kryptic, group users/backup) the NFS directory works fine with those permissions, on the 11.3 laptop (username tasha, group users/backup) I get permission denied, same with 770, the only one that will work is 777?

Server:

drwx--S--- 4 kryptic Backup 4096 2010-08-01 15:03 Dales_Backup
drwxr-sr-x 5 kryptic Backup 4096 2010-08-01 17:14 External_Clone
drwxrwsrwx 4 root    Backup 4096 2010-08-02 08:21 Media
drwx--S--- 3 tasha   Backup 4096 2010-08-02 08:57 Tashas_Backup

11.3 Laptop:

drwx--S--- 3  1002  1001  4096 2010-08-02 08:57 Tashas_Backup

1002 is tasha in users and groups on server
1001 is Backup group

11.2 Laptop:

drwx--S--- 4 kryptic 1001 4096 2010-08-01 15:03 Dales_Backup
11

Those 1002 and 1001 are not configured as user/group on that system. Even if you have a user with the same user name, it obviously has a different uid (like 1003 or so). When you have systems cooperating that close as you have (with NSF) you should see that on every system the users/groups have the same names and the same ids. Else all protection based on owner ship by user/group is futile.

Thus either be very carefull while creating new users/groups. See that you have the same everywhere.
The original inventer of NFS (Sun Microsystems) did also invent NIS (aka Yellow Pages) to provide a centralised user administration. But with only three systems, that is a bit heavy.

12

Perfect, that is what I was wondering UID was my problem, changed it to match the server and works perfect now.

Again, thank you for your time I appreciate it.

13

You are welcome.