[SOLVED] Anyone having NFS trouble?

ricky_cardo · 07-27-2019, 09:44 PM

I've been using NFS for a while and I think it broke for me couple weeks back. (20190714)

I have banana pi pro (arm-slack serving Slackware tree on nfs and it stopped working, I suspect after an update.

Can someone verify NFSd is still good then I'll know I got some config issues.

I currently get this response:

Code:

mount.nfs: Stale file handle

I modified config and exported a dir from my Slackware64 box as a test and mounted it on the bananapi no issues.

(checked rpcd and nfsd they are executable and show serving)

FROM SERVER:

Code:

All mount points on banana.lehcar.no-ip.org:
192.168.1.240:/boxee/sick

tried several things:

Code:

exportfs -ua
cat /proc/fs/nfs/exports
exportfs -a
cat /proc/fs/nfs/exports
showmount -a
 vim /var/lib/nfs/rmtab
/etc/rc.d/rc.nfsd stop
 /etc/rc.d/rc.rpc stop
 /etc/rc.d/rc.nfsd start
/etc/rc.d/rc.rpc start

drmozes · 07-28-2019, 09:28 AM

Hello

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.

Code:

xserv:/devel/armedslack/  /mnt/armedslack   nfs         vers=3,noatime,rsize=8192,wsize=8192,hard,nointr,defaults,tcp 0 0

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).

glorsplitz · 07-28-2019, 12:45 PM

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.

ricky_cardo · 07-28-2019, 04:29 PM

Thanks guys that's exactly what I was looking for!!! I'll report back findings.

Code:

192.168.1.245:/boxee/sick /banana/sick nfs vers=3,noatime,rsize=8192,wsize=8192,timeo=14,nointr,hard,defaults,tcp  0 0

Added
vers=3,noatime,nointr,hard,defaults,tcp

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

ricky_cardo · 07-29-2019, 10:59 PM

Well I can't seem to serve NFS from my bananapi

- 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)

my new /etc/exports

Code:

/home/rich/public_html/Slackware 192.168.1.0/255.255.255.0(rw,nohide,no_root_squash,sync,no_subtree_check)

on the remote machine:
in /etc/fstab

Code:

192.168.1.245:/home/rich/public_html/Slackware /banana/Slackware nfs vers=3,rsize=8192,wsize=8192,timeo=14,nointr,hard,defaults,tcp  0 0

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?

ricky_cardo · 08-01-2019, 08:42 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)

Laptop client: (fstab)

Code:

192.168.1.245:/home/rich/public_html/Slackware /banana/Slackware nfs vers=3,rsize=8192,wsize=8192,timeo=14,nointr,hard,defaults,tcp  0 0

glorsplitz · 08-01-2019, 09:51 PM

oops, forgot all about this, maybe check my thread here, fsid=0 explanation in nfs exports please see if gets you anywhere?

ricky_cardo · 08-02-2019, 05:14 AM

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)

nfs-utils-2.4.1-arm-1.txz
(needs fsid=0)
/home/rich/public_html/Slackware 192.168.1.0/255.255.255.0(rw,nohide,no_root_squash,sync,no_subtree_check,fsid=0)

glorsplitz · 08-02-2019, 10:09 AM

Good to hear BUT why is this?

Quote:

Originally Posted by ricky_cardo

- the new version of nfs-utils requires me to add fsid=0

No one answered why in my other post.

ricky_cardo · 08-02-2019, 03:56 PM

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)

ricky_cardo · 08-04-2019, 04:35 PM

Found this on the arch forum.
https://archlinuxarm.org/forum/viewt...563e6&start=10

might try patch

glorsplitz · 08-04-2019, 04:50 PM

let us know how it goes if you try the patch

might wait for patch to float up in regular upgrades

ricky_cardo · 08-04-2019, 08:18 PM

Works like a champ!!!

added this to nfs-util.SlackBuild (@ line 100)

Code:

echo "PATCH TIME"
patch -d support/misc -i $CWD/patch.nfsd_path.c
patch -d support/misc -i $CWD/patch.xstat.c
patch -d utils/blkmapd -i $CWD/patch.device-discovery.c
patch -d utils/idmapd -i $CWD/patch.imapd.c

and here are the patch files just tar -xvf in the SlackBuild directory
http://lehcar.no-ip.org:8080/~rich/patch_nfs.tar.gz

got them from here:
https://www.spinics.net/lists/linux-nfs/msg73979.html

Once patched you don't need to use the "fsid=0" option.

- It also for me allows nfs mount as before on my android tv device.

drmozes · 08-05-2019, 03:48 PM

Hi

I will add this to the todo and push it out in the next updates.