nfs mount at boot shows as mounted but is not...
Hi all,
I setup my client to mount some nfs mounts at boot but although they seem to be mounted, they are not! Before I give the details, I'll start by saying this is not a wifi problem. I'm using a good old wired connection. ;)
The server runs NFS3 with the following line in '/etc/exports':
Code:
"/raid0/data/foobar" 192.168.1.5(rw,no_root_squash,sync,anonuid=99,anongid=99)
The Client has the following config in '/etc/fstab':
Code:
192.168.1.100:/raid0/data/foobar /home/jdoe/foobar nfs rw,noexec,users,nolock,nosuid 0 0
The NFS Server is a NAS and the client is a Kubuntu 10.10 with the latest patches.
This is what I get after booting:
Code:
$ df -h /home/jdoe/foobar/
Filesystem Size Used Avail Use% Mounted on
192.168.1.100:/raid0/data/foobar
1.8T 264G 1.5T 16% /home/jdoe/foobar
Code:
$ ls -l foobar/dl
ls: cannot access foobar/dl: No such file or directory
Code:
$ mount |grep foobar
192.168.1.100:/raid0/data/foobar on /home/jdoe/foobar type nfs (rw,users,noexec,nosuid,nodev,nolock,addr=192.168.1.100)
Code:
$ cat /etc/mtab |grep foobar
192.168.1.100:/raid0/data/foobar /home/jdoe/foobar nfs rw,users,noexec,nosuid,nodev,nolock,addr=192.168.1.100 0 0
Code:
$ sudo umount -v -t nfs /home/jdoe/foobar/
[sudo] password for jdoe:
umount.nfs: prog 100005, trying vers=3, prot=17
umount.nfs: trying 192.168.1.100 prog 100005 vers 3 prot UDP port 630
umount.nfs: /home/jdoe/foobar: not mounted
Could not find /home/jdoe/foobar in mtab
umount.nfs: /home/jdoe/foobar: not mounted
Code:
$ sudo mount -v /home/jdoe/foobar
mount.nfs: timeout set for Wed Nov 17 19:10:37 2010
mount.nfs: trying text-based options 'nolock,vers=4,addr=192.168.1.100,clientaddr=192.168.1.5'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'nolock,addr=192.168.1.100'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.100 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.100 prog 100005 vers 3 prot UDP port 630
192.168.1.100:/raid0/data/foobar on /home/jdoe/foobar type nfs (rw,noexec,nosuid,nodev,users,_netdev,nolock)
Code:
$ df -h /home/jdoe/foobar/
Filesystem Size Used Avail Use% Mounted on
192.168.1.100:/raid0/data/foobar
2.7T 1.9T 817G 70% /home/jdoe/foobar
Code:
$ ls -l foobar/dl
total 2658664
drwxrwxrw-+ 3 jdoe jdoe 4096 2009-04-05 15:37 2008-08-06 - Moto
-rwxrwx---+ 1 jdoe jdoe 225533 2008-12-04 12:09 2008487
[...]
I have tried the following nfs options in the fstab as you might have noted above: _netdev,auto,bg,retry=10. None of them seem to fix the problem. I realise a quick hack at boot time would fix this in an instant but I'd like to figure out why this is failing.
Any thoughts? Thanks! |
