Can't (auto)mount NFS in 11.2 anymore

English Network/Internet
#1

11.2 issues keep piling up…

I had an NFS server on my desktop and used autofs to mount it on my laptop using openSUSE 11.1 on both. Now I installed 11.2 on both, made exactly identical settings and configurations, copied the same config files, even gone further and turned off the firewall - CAN’T mount!

Desktop:
User: linuxoid
UID: 1000
Groups: datauser
GID: 1000

Laptop
User: linuxoid
UID: 1000
Groups: datauser
GID: 1000

My shared folder ‘data’ has permissions:
User: linuxoid
Group: datauser
Owner: rwx
Group: rwx
Others: —

NFS server:
IP: 192.168.1.2
NFSv4 enabled
Firewall port open (but firewall disabled)
Directories: /mnt/data
Hosts: 192.168.1.* fsid=0,crossmount,rw,root_squash,no_subtree_check

NFS client:
IP: 192.168.1.3
NFSv4 enabled
Firewall port open (but firewall disabled)
Folders: /mnt/DataServer (created by autofs), /mnt/Server

auto.master:
/mnt /etc/auto.misc --timeout 60

auto.misc:
DataServer -fstype=nfs4,rw,soft,intr,nosuid,nodev,tcp,retry=10,rsize=32768,wsize=32768 192.168.1.2:/

Autofs doesn’t mount. ‘showmount 192.168.1.2 -e’ just hangs.

Manual mount with ‘mount -t nfs4 192.168.1.2:/ /mnt/Server’ also hangs.

What am I doing wrong or missing? I can ping each both ways.

#2

I’ve just found out that the portmapper in 11.1 has been replaced by an Rpcbind in 11.2. Could that be a problem?

" NFS Background Mounting
NFS clients use the remote procedure call (RPC) suite of network application helper programs to mount remote filesystems. If the mount cannot occur during the default RPC timeout period, then the client retries the mount process until the NFS number of retires has been exceeded. The default is 10,000 minutes, which is approximately a week. The difficulty here is that if the NFS server is unavailable, the mount command will hang for a week until it returns online. It is possible to use a bg option spawn the retries off as a subprocess so that the main mount command can continue to process other requests."

A week? WTF??? I have to read more about it.

#3

Plot thickens… After reading and doing this: Quick HOWTO : Ch29 : Remote Disk Access with NFS - Linux Home Networking,

  1. ‘showmount -a’ on the server doesn’t show any mount points.
  2. ‘showmount 192.168.1.2:/ -e’ says ‘showmount: can’t get address for 192.168.1.2:/’
#4

On Wed, 2009-12-16 at 14:06 +0000, linuxoidoz wrote:
> Plot thickens… After reading and doing this: ‘Quick HOWTO : Ch29 :
> Remote Disk Access with NFS - Linux Home Networking’
> (http://tinyurl.com/khsfw),
>
> 1. ‘showmount -a’ on the server doesn’t show any mount points.
> 2. ‘showmount 192.168.1.2:/ -e’ says ‘showmount: can’t get address for
> 192.168.1.2:/’

showmount -e 192.168.1.2

(I think your syntax might be wrong)

Can you mount it manually?

Where are your automount maps stored? Are they coming
from NIS or LDAP? Have you made sure they are reachable?

#5

F%**^^%^&$$&$&&$K!!! (uncolloquial expression followed by more R+ rated exclamations) It started working after reboot. I’ll be ****ed! I forgot the windows school of doing thing many years ago. I thought Linux is over it by now… oh, well :slight_smile:

And to answer your question, no I could not mount it manually. By maps you mean the export file? No, I don’t use NIS or LDAP, I just set usernames, groups and UIDs and GIDs the same on both machines for authentication.

#6

Yep, it’s still working alright. And now I also have a Seagate BlackArmor NAS 110 running NFS and I can mount it dynamically with autofs as well as my desktop’s NFS. Perfect!

I’ll write a Howto on NFS and Autofs on the weekend.