I have setup my NFS server with the following configuration: /etc/exports /home/bob/Documents 192.168.1.14(rw,no_root_squash,sync,no_subtree_check) /home/bob/download 192.168.1.14(ro,no_root_squash,sync,no_subtree_check) I have created appropriate mountpoints on the client. The download directory mounts impeccably and I can view its contents on the client machine. The Documents directory *appears* to mount, but is empty when I open it in a file browser. I'm pretty sure it is mounted, because Konqueror reports appropriate free/total space in the Properties dialog. On the client, mount -f contains the following lines: .. 192.168.1.12:/home/bob/download on /home/bob/BHF_download type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp) 192.168.1.12:/home/bob/Documents on /home/bob/BHF_Documents type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp) .. Why does it work in one case, but not the other? Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob Williams wrote:
I have setup my NFS server with the following configuration:
/etc/exports
/home/bob/Documents 192.168.1.14(rw,no_root_squash,sync,no_subtree_check) /home/bob/download 192.168.1.14(ro,no_root_squash,sync,no_subtree_check)
no_root_squash is generally a bad idea - it's a major security hole. Try to rearrange whatever work you're trying to do so it's not necessary. sync is slow and definitely shouldn't be needed for ro and probably not for rw
I have created appropriate mountpoints on the client. The download directory mounts impeccably and I can view its contents on the client machine. The Documents directory *appears* to mount, but is empty when I open it in a file browser. I'm pretty sure it is mounted, because Konqueror reports appropriate free/total space in the Properties dialog.
Don't use browsers, use the command-line tools to see what is happening. One less component to cause misunderstandings.
On the client, mount -f contains the following lines: .. 192.168.1.12:/home/bob/download on /home/bob/BHF_download type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp) 192.168.1.12:/home/bob/Documents on /home/bob/BHF_Documents type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp)
Why is download mounted rw if it is only exported ro? That suggests some inconsistency in what you're showing us. Why are the filesystems mounted using nfsvers=2? That's a very old version; it would be better to use a newer version. What nfs-related messages are in /var/log/messages on both client and server
Why does it work in one case, but not the other?
what does ls -nd /home/bob/Documents show on the server? what does ls -nd /home/bob/BHF_Documents show on the client? Is there at least one file in the directory that should be able to be seen by the uid/gid on the client? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 24 November 2008 15:58:39 Dave Howorth wrote:
Bob Williams wrote:
I have setup my NFS server with the following configuration:
/etc/exports
/home/bob/Documents 192.168.1.14(rw,no_root_squash,sync,no_subtree_ch eck) /home/bob/download 192.168.1.14(ro,no_root_squash,sync,no_subtree_che ck)
no_root_squash is generally a bad idea - it's a major security hole. Try to rearrange whatever work you're trying to do so it's not necessary.
Do I change that to root_squash? Or leave it out?
sync is slow and definitely shouldn't be needed for ro and probably not for rw
OK, I've removed that option, is that correct?
I have created appropriate mountpoints on the client. The download directory mounts impeccably and I can view its contents on the client machine. The Documents directory *appears* to mount, but is empty when I open it in a file browser. I'm pretty sure it is mounted, because Konqueror reports appropriate free/total space in the Properties dialog.
Don't use browsers, use the command-line tools to see what is happening. One less component to cause misunderstandings.
On the client, mount -f contains the following lines: .. 192.168.1.12:/home/bob/download on /home/bob/BHF_download type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp) 192.168.1.12:/home/bob/Documents on /home/bob/BHF_Documents type nfs (rw,addr=192.168.1.12,nfsvers=2,proto=tcp,mountproto=udp)
Why is download mounted rw if it is only exported ro? That suggests some inconsistency in what you're showing us.
I don't know why it mounted rw, unless that's the default for mount. I didn't specify any options. Anyway, I've decided to export download as rw rather than ro.
Why are the filesystems mounted using nfsvers=2? That's a very old version; it would be better to use a newer version.
I've just used whatever came with the installation. Both machines are running openSUSE 11.0.
What nfs-related messages are in /var/log/messages on both client and server
On the server: # grep nfs /var/log/messages Nov 23 17:52:21 barrowhillfarm nfsd[3508]: Unknown keyword "no_subtree_check" in export file Nov 23 17:52:21 barrowhillfarm nfsd[3508]: Unknown keyword "no_subtree_check" in export file (Interesting, I got that keyword from http://nfs.sourceforge.net/nfs-howto/ar01s03.html) Nov 24 09:54:22 barrowhillfarm mountd[3506]: NFS mount of /home/bob/Documents attempted from 192.168.1.14 Nov 24 10:02:35 barrowhillfarm mountd[3506]: NFS mount of /home/bob/Documents attempted from 192.168.1.14 Nov 24 10:05:39 barrowhillfarm mountd[3506]: NFS mount of /home/bob/download attempted from 192.168.1.14 Nov 24 10:06:30 barrowhillfarm mountd[3506]: NFS mount of /home/bob/Documents attempted from 192.168.1.14 On the client: # grep nfs /var/log/messages Nov 24 10:02:24 sputnik sm-notify[2587]: sm-notify running as root. chown /var/lib/nfs/sm to choose different user Nov 24 10:02:24 sputnik rpc.statd[2604]: statd running as root. chown /var/lib/nfs/sm to choose different user
Why does it work in one case, but not the other?
what does ls -nd /home/bob/Documents show on the server?
bob@barrowhillfarm:~> ls -nd /home/bob/Documents drwxrwx--- 66 1000 100 4096 2008-11-09 18:56 /home/bob/Documents
what does ls -nd /home/bob/BHF_Documents show on the client?
bob@sputnik:~> ls -nd /home/bob/BHF_Documents drwxrwx--- 66 1000 100 4096 2008-11-09 18:56 /home/bob/BHF_Documents
Is there at least one file in the directory that should be able to be seen by the uid/gid on the client?
The whole directory is shared, if that's what you mean. It contains 633.4 MB.
Cheers, Dave
Many thanks Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well, it's working, now. Many thanks, Dave, for your interest and help. I changed my /etc/exports to /home/bob/Documents 192.168.1.14(rw,root_squash) /home/bob/download 192.168.1.14(rw,root_squash) and rebooted to server, followed by the client. I'm doubly happy, now :) 1. My machines can talk to each other 2. I've learnt a new trick. Ain't Linux great? Bob -- Registered Linux User #463880 FSFE Member #1300 GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E openSUSE 11.0, Kernel 2.6.25.18-0.2-default, KDE 3.5.10 Intel Celeron 2.53GHz, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (2)
-
Bob Williams
-
Dave Howorth