Slackware - ARMThis forum is for the discussion of Slackware ARM.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've not had any issues myself and NFS is used continuously.
Usually if there's a stale file handle, it means something changed on the server outside of the awareness of the running process on the client.
For example, if you were in a directory on the client, then removed it on the server, the next time you did anything (even pressed ENTER on the shell prompt), you'd normally see the type of error you reported.
I used to spend some time with NFS as a sysadmin, and came up with these settings and haven't changed them in years.
As long as the machine is on the same physical LAN, the "hard" option should be fine.
Note that it's using NFSv3 too - I don't need anything in v4. The Slackware ARM installer also uses version 3, as I had some issue with v4 (I forget what it was - probably related to mounting).
I was setting up my newer banana pi pro nfs server recently and had some issues like stale file handle but I went over everything and got it working. Maybe something you overlooked? My system is up to date.
Last edited by glorsplitz; 07-28-2019 at 12:48 PM.
Checked to make sure /etc/nfsmount.conf was stock configuration.
/etc/export
Code:
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
/home/rich/public_html/Slackware 192.168.1.0/255.255.255.0(rw,nohide,no_root_squash,sync,no_subtree_check)
/boxee/sick 192.168.1.0/255.255.255.0(insecure,ro,nohide,root_squash,sync,no_subtree_check)
/boxee 192.168.1.0/24(insecure,ro,sync,no_subtree_check,root_squash)
- digging in a bit more
Last edited by ricky_cardo; 07-28-2019 at 05:29 PM.
- I can serve from Slackware64-current and mount as a client on the bananapi-pro but not the reverse.
-I backed up my files and wiped most of the directories and fresh installed. I picked do not format and kept the following directories:
root, home (planning to serve /home/rich/public_html/Slackware)
The weird thing is I seem to be able to do the reverse that is serve from slackware x86_64 to the bananapi just not have the bananapi-pro be the server.
--Anybody have any new suggestions? [I ruled out some hidden config by having a fresh /etc/ ]
--you guys sure you can have server on the arm side?
Last edited by ricky_cardo; 07-30-2019 at 08:24 PM.
I rebuilt nfs-utils-2.3.4-arm-1.txz and downgraded my NFSd is working again.
Seems like something is breaking NFSd on arm at least for me on the banana-pi with version nfs-utils-2.4.1-arm-1.txz
**Note I am serving from the bananapi-pro
** client slackware64-current
--Curious if anyone can reproduce? (I did do a clean install of slackware-arm((just kept home and root)))
Arm host:
Code:
# See exports(5) for a description.
# This file contains a list of all directories exported to other computers.
# It is used by rpc.nfsd and rpc.mountd.
/home/rich/public_html/Slackware 192.168.1.0/255.255.255.0(rw,nohide,no_root_squash,sync,no_subtree_check)
Wow that's interesting. (and for me the version of nfs-utils matters)
So for my case like you suggested I needed to append fsid=0
- the new version of nfs-utils requires me to add fsid=0
Results: [server side option needed]
nfs-utils-2.3.4-arm-1.txz (does NOT need fsid=0)
/home/rich/public_html/Slackware 192.168.1.0/255.255.255.0(rw,nohide,no_root_squash,sync,no_subtree_check)
I rolled back to nfs-utils-2.3.4-arm-1.txz for the short term, might try some wireshark traces see if I can see a difference there.
Also I have a few .mkv files I serve over to an androidtv via NFS and that clients is not liking the newer version of nfs either.
- old dvds I ripped with handbrake (years back, digital library)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.