Click to See Complete Forum and Search --> : NFS newbie troubles
(1) Accessing Windows partition on the NFS server from client
NFS client can't access /mnt/windows dirs and files on the NFS server.
(2) NFS lock
Even after the client unmounts NFS mount point, we can't access files on
the server from THE server itself.
(3) NFS client don't access new hostname of the server
After changing the server host name by hostname command, the mount command
line on the client can't recognize the new host name. Only server's IP
address works on the command line:
mount -t nfs 192.168.11.3:/pub /nfs
I'd like to know the causes/reasons of above phenomenon and workarounds for
those.
Thanks in advance.
psi42
10-12-2004, 06:05 AM
Originally posted by hiwa
(1) Accessing Windows partition on the NFS server from client
NFS client can't access /mnt/windows dirs and files on the NFS server.
Can normal users on the server access /mnt/windows? By default, requests from NFS clients with UID 0 (root) are treated as requests from "nobody." So if "nobody" on the server can't access /mnt/windows, neither can your clients.
You either need to add umask=000 to the windows partition's options in /etc/fstab, or put no_root_squash in /etc/exports (which lessens your security and probably is not the best solution).
(2) NFS lock
Even after the client unmounts NFS mount point, we can't access files on
the server from THE server itself.
.... error message?
(3) NFS client don't access new hostname of the server
After changing the server host name by hostname command, the mount command
line on the client can't recognize the new host name. Only server's IP
address works on the command line:
mount -t nfs 192.168.11.3:/pub /nfs
That's because your client has no way of knowing the server's hostname. You either need to have it defined in the clients' /etc/hosts, or set up a DNS server.
Have fun,
~psi42
You either need to add umask=000 to the windows partition's options in /etc/fstab, or put no_root_squash in /etc/exports (which lessens your security and probably is not the best solution).
Yes I did no_root_squash in the /etc/exports entry:
/ 192.168.11.0/24(ro,no_root_squash)
.... error message?
No message. Everyday mundane programs such as editor, image viewer etc. couldn't open any file.
set up a DNS server
How? Could you give pointer?
psi42
10-12-2004, 08:22 AM
Originally posted by hiwa
Yes I did no_root_squash in the /etc/exports entry:
/ 192.168.11.0/24(ro,no_root_squash)
Post your fstab.
No message. Everyday mundane programs such as editor, image viewer etc. couldn't open any file.
That's _very_ odd.
How? Could you give pointer?
Here is the DNS howto:
http://www.tldp.org/HOWTO/DNS-HOWTO.html
I am running dnsmasq... it was fairly easy to set up.
Icarus
10-12-2004, 09:13 AM
Originally posted by hiwa
No message. Everyday mundane programs such as editor, image viewer etc. couldn't open any file. You have messages, you just don't know where to look ;)
Check /var/log/messages, almost everything system related gets logged there. I have tons of NFS messages in mine from when my NFS server crashed.