Hi: (Suse 7.3) I have a server machine named tong 192.168.0.12 which has /etc/exports: / 192.168.0.0/255.255.255.0(ro) /home 192.168.0.0/255.255.255.0(rw) And on the client machine ting 192.168.0.11 I can mount the tong:/home , but I can't mount tong:/ Also, tong gives an error when I run the nfsserver: tong:/ # /etc/init.d/nfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server192.168.0.11:/: Invalid argument done Why does the nfsserver script mention ting's IP when trying to restart? If I take out the line attempting to export / in tong:/etc/exports, then the nfsserver script doesn't give an error. Now what's really strange is that we can reverse the situation: Ting also runs nfsserver, and has the exact same /etc/exports . However, tong can mount ting:/ with no problem! For the life of me I cannot find a difference in the connfigurations of the two machine's NFS setups. Hosts.deny/allow are the same as well. Digging a little deeper, I find that when I run on tong: tong:~ # exportfs 192.168.0.0/255.255.255.0:/ 192.168.0.11:/: Invalid argument But when I do this: tong:~ # exportfs ting:/ Now it works! Ok, so I can make it work by hand, but the trouble is still that the line in /etc/exports doesn't work on tong, but works on ting. Ugh! Thanks. -- _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
On Saturday 20 July 2002 19.42, Chris Carlen wrote:
Hi: (Suse 7.3)
I have a server machine named tong 192.168.0.12 which has /etc/exports:
/ 192.168.0.0/255.255.255.0(ro) /home 192.168.0.0/255.255.255.0(rw)
And on the client machine ting 192.168.0.11 I can mount the tong:/home , but I can't mount tong:/
I had a very similar problem. I exported: /home 192.168.0.0/24(rw) /home/multimedia 192.168.0.0/24(rw) As long as I had 7.3 on my server it worked very good. When I installed 8.0 on the server it stopped working most of the time. Occasionally I could mount the /home. /home/multimedia mounted without problem. The solution for me was to move /home/multimedia to /multimedia and then there were no problems. It seems to me that there is some rule in NFS that says that you are not allowed to export a directory above an other directory in the hierarchy. I would like to know if there is a bug in the new NFS (in 8.0) or if there was some checking in the old that was not working. Regards /Nils-Olov Fransson
Nils-Olov Fransson
I would like to know if there is a bug in the new NFS (in 8.0) or if there was some checking in the old that was not working.
Nope, more probably it was another nfs server. There are two versions available, user space nfsd and knfsd, which is part of the kernel. Only unfsd supports export of subdirectories of exported directories. But only knfsd supports file locking and is generally the better choice. If you absolutely need the subdir export feature, install the user space nfs server. Philipp -- Philipp Thomas work: pthomas@suse.de Development SuSE Linux AG private: philippt@t-online.de
I would like to know if there is a bug in the new NFS (in 8.0) or if there was some checking in the old that was not working.
Nope, more probably it was another nfs server. There are two versions available, user space nfsd and knfsd, which is part of the kernel. Only unfsd supports export of subdirectories of exported directories. But only knfsd supports file locking and is generally the better choice.
This was exactly the answer i wanted.
If you absolutely need the subdirectories export feature, install the user space nfs server.
No I changed it so I don't need to export subdirectories. Thank you very much Philipp /Nils-Olov
The most likely problem is that your /etc/exports file has a hidden control character somewhere in it, which is messing things up. Try deleting the entire file and retyping it in. The same /etc/exports as your email works for me, so it isn't a problem with how you've set it up. Ewan On Sat, 2002-07-20 at 18:42, Chris Carlen wrote:
Hi: (Suse 7.3)
I have a server machine named tong 192.168.0.12 which has /etc/exports:
/ 192.168.0.0/255.255.255.0(ro) /home 192.168.0.0/255.255.255.0(rw)
And on the client machine ting 192.168.0.11 I can mount the tong:/home , but I can't mount tong:/
Also, tong gives an error when I run the nfsserver:
tong:/ # /etc/init.d/nfsserver restart Shutting down kernel based NFS server done Starting kernel based NFS server192.168.0.11:/: Invalid argument done
Why does the nfsserver script mention ting's IP when trying to restart?
If I take out the line attempting to export / in tong:/etc/exports, then the nfsserver script doesn't give an error.
Now what's really strange is that we can reverse the situation:
Ting also runs nfsserver, and has the exact same /etc/exports . However, tong can mount ting:/ with no problem! For the life of me I cannot find a difference in the connfigurations of the two machine's NFS setups. Hosts.deny/allow are the same as well.
Digging a little deeper, I find that when I run on tong:
tong:~ # exportfs 192.168.0.0/255.255.255.0:/ 192.168.0.11:/: Invalid argument
But when I do this:
tong:~ # exportfs ting:/
Now it works!
Ok, so I can make it work by hand, but the trouble is still that the line in /etc/exports doesn't work on tong, but works on ting.
Ugh!
Thanks. -- _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com
Ewan Leith wrote:
The most likely problem is that your /etc/exports file has a hidden control character somewhere in it, which is messing things up. Try deleting the entire file and retyping it in.
The same /etc/exports as your email works for me, so it isn't a problem with how you've set it up.
Very good idea. But it doesn't work. Now wait till you see this, which I posted on comp.os.linux.networking: Observe the following sequence, which may reveal some clues as to what is going on: (ting is the client to export to, and server tong and client ting are on 192.168.0.0 LAN) tong:~ # mv /etc/exports /etc/exports.hide tong:~ # /etc/init.d/nfsserver stop Shutting down kernel based NFS server done tong:~ # /etc/init.d/nfsserver start Starting kernel based NFS serverexportfs: can't open /etc/exports for reading done tong:~ # exportfs ting:/ exportfs: can't open /etc/exports for reading tong:~ # touch /etc/exports I have removed /etc/exports from the picture, so now only manual exportfs commands will control NFS. But it dedmanded that I at least have an extant /etc/exports file, though empty. Ok, here we go... tong:~ # exportfs ting:/ tong:~ # exportfs -u ting:/ No problem exporting / directly to ting. tong:~ # exportfs 192.168.0.0/255.255.255.0:/ tong:~ # exportfs -u 192.168.0.0/255.255.255.0:/ No problem exporting / directly to the LAN. tong:~ # exportfs 192.168.0.0/255.255.255.0:/home tong:~ # exportfs 192.168.0.0/255.255.255.0:/ 192.168.0.11:/: Invalid argument It seems I can't export / after first exporting a subdir of /. Can I export / first, then a subdir after? tong:~ # exportfs -u 192.168.0.0/255.255.255.0:/home tong:~ # exportfs 192.168.0.0/255.255.255.0:/ tong:~ # exportfs 192.168.0.0/255.255.255.0:/home 192.168.0.11:/home: Invalid argument It seems I cannot. What remains BIZARRE is that on ting's NFS server: ting:~ # mv /etc/exports /etc/exports.hide ting:~ # touch /etc/exports ting:~ # /etc/init.d/nfsserver stop Shutting down kernel based NFS server done ting:~ # /etc/init.d/nfsserver start Starting kernel based NFS server done Now we have prepared an empty /etc/exports . Now watch this: ting:~ # exportfs 192.168.0.0/255.255.255.0:/ ting:~ # exportfs 192.168.0.0/255.255.255.0:/home No error! And ting can in fact mount the individual exports (onto different trees) Let's undo it and try it in reverse: ting:~ # exportfs -u 192.168.0.0/255.255.255.0:/home ting:~ # exportfs -u 192.168.0.0/255.255.255.0:/ ting:~ # exportfs 192.168.0.0/255.255.255.0:/home ting:~ # exportfs 192.168.0.0/255.255.255.0:/ Again no error, with either sequence. It is also not a problem with the /etc/exports file, since the trouble is clearly demonstrated through manual manipulations. Now the Linux guru who can explain and/or fix the cause of *this* inconsistency get's a big chocolate fish and a gold star for the day. Good day! _____________________ Christopher R. Carlen crobc@earthlink.net Suse 7.3 Linux 2.4.10
participants (4)
-
Chris Carlen -
Ewan Leith -
Nils-Olov Fransson -
Philipp Thomas