Tiny Core Extensions > TCE Q&A Forum
nfs questions?
bigpcman:
Ok, I'm getting a little farther now. The nfs probe now seems happy and the pingNFS gets a full response but the show exports returns nothing. It looks like the exportfs is not updating correctly. I now get "could not open or lock errors" on exports, rmtab, etab, and xtab. I tried exportsfs with nfs started and stopped, no difference. Any ideas?
edit:
I added "/home/tc 192.168.0.114(rw,insecure,no_root_squash)" to the "exports" file as I said before and now get "access denied enter another user name and password" from the client when I try and access "192.168.0.114:/home/tc". So I entered user name tc and my password and get the same response. But at least the client has a valid path now.
edit2: attached nfs client trace log.
bigpcman:
tc2rc1
I'm still trying to get nfs working on tc2rc1 without success. The "exports" file modifications do not transfer to /var/lib/nfs/etab after executing the "exportfs -ra" command. Actually all of the files etab,rmtab and xtab are empty. I'm using the instructions from the nfs faq below. Does anyone else have this working? If so I will put this aside.
--- Code: ---C1. How are exported file systems and client mount points tracked on the server?
A. /etc/exports contains information about how file systems should normally be exported. This is only read by exportfs.
/var/lib/nfs/etab contains information about what filesystems should be exported to whom at the moment.
/var/lib/nfs/rmtab contains a list of which filesystems actually are mounted by certain clients at the moment.
/proc/fs/nfs/exports contains information about what filesystems are exported to actual client (individual, not subnet or whatever) at the moment.
/var/lib/nfs/xtab is the same information as /proc/fs/nfs/exports but is maintained by nfs-utils instead of directly by the kernel. It is only used if /proc isn't mounted.
C2. Can I modify export permissions without needing to remount clients in order to have them take effect?
A. Yes. The safest thing to do is edit /etc/exports and run "exportfs -r".
Note that when a mount request arrives, mountd check .../etab to see if that host is allowed access. If it is, an entry is placed in .../rmtab and the filesystem is exported thus creating an entry in /proc/fs/nfs/exports.
--- End code ---
Jason W:
The files in /var/lib/nfs exist in the extension so there may be a permissions error. I made the extension before we had startup scripts I believe, and if the files must exist then creating them with the touch command in the script may work better. If the files themselves to not have to exist then creating the directory may be all that is needed. I will check on it tonight.
bigpcman:
--- Quote from: Jason W on May 01, 2009, 10:04:22 AM ---The files in /var/lib/nfs exist in the extension so there may be a permissions error. I made the extension before we had startup scripts I believe, and if the files must exist then creating them with the touch command in the script may work better. If the files themselves to not have to exist then creating the directory may be all that is needed. I will check on it tonight.
--- End quote ---
Thanks. I did a chmod 777 on all the etab,rmtab and xtab files as a brute force test and that did not change anything. Is there anything else you would like me to try? I've dedicated today to testing tc2rc1.
Jason W:
One more thing I will look at tonight is that the files may need to exist in /usr/local/var/lib/nfs since it was compiled to /usr/local. I will check and see and hopefully get it straight.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version