Packages: Last nfs-kernel-server not work (2.3.3-2)

Created on 8 May 2019 · 25Comments · Source: openwrt/packages

The last nfs-kernel-server (2.3.3-2) update does not work, no more access to the share. A showmount -e results in 192.168.0.xxx 'clnt_create: RPC: Unable to send'.

Source

misterhsp

Most helpful comment

See my post: https://github.com/openwrt/packages/issues/10942
Vanilla install of 18.06.5: Bang! Immideate errors and warnings, no nfsv3 anymore, breaks all former installtions using v3.
Prior to the release there even cannot have been a simple install! Let alone any serious testing.

Chris56 on 4 Jan 2020

👍2

All 25 comments

@tripolar @BKPepe

diizzyy on 8 May 2019

According to the version of nfs-kernel-server you should have running OpenWrt 18.06.02 on your router, right? The thing is that nfs-kernel-server wasn't tested anyhow on that stable release, which is a pity. However a few days ago there was an issue, so I tried to fix it at least, but after that maintainer took a different approach and since that, I didn't look at it. To be honest, I lost my interest in nfs-kernel-server as there is also one issue, which I mention in my PR, but there wasn't done anything to it. I don't give up so easily and will try it again. I won't be able to look at it until next week.

BKPepe on 8 May 2019

Am 08.05.19 um 09:52 schrieb Josef Schlehofer:
>

According to the version of nfs-kernel-server you should have running
OpenWrt 18.06.02 on your router, right? The thing is that
nfs-kernel-server wasn't tested anyhow on that stable release, which
is a pity. However a few days ago there was an issue, so I tried to
fix it at least, but after that maintainer took a different approach
and since that, I didn't look at it. To be honest, I lost my interest
in nfs-kernel-server as there is also one issue, which I mention in my
PR, but there wasn't done anything to it. I don't give up so easily
and will try it again. I won't be able to look at it until next week.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openwrt/packages/issues/8930#issuecomment-490386684,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGJLRP2KEA6BQWXPKEERULPUKBDLANCNFSM4HLORUYQ.

Yes right, 18.06.02. But it could also be due to rpcbind, but I am so sure.

...

misterhsp on 8 May 2019

The last nfs-kernel-server (2.3.3-2) update does not work, no more access to the share. A showmount -e results in 192.168.0.xxx 'clnt_create: RPC: Unable to send'.

Keep in mind showmount -e did not work, because rpcbind was build without rmtcalls support. This was fixed in snapshots 6 days ago.

However this did not prevent mounting the share, the share was just not browse-able.

Andy2244 on 10 May 2019

Am 10.05.19 um 11:34 schrieb Andy Walsh:
>

The last nfs-kernel-server (2.3.3-2) update does not work, no more
access to the share. A showmount -e results in 192.168.0.xxx
'clnt_create: RPC: Unable to send'.
Keep in mind |showmount -e| did not work, because rpcbind was build
without |rmtcalls| support. This was fixed in snapshots 6 days ago.

However this did not prevent mounting the share, the share was just
not browse-able.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openwrt/packages/issues/8930#issuecomment-491225879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGJLRO2MP445WZBJZV4KO3PUU6RBANCNFSM4HLORUYQ.

before the nfs-server update everything works fine. Now it doesn't work
anymore.

showmount -e xxxxxxx
clnt_create: RPC: Unable to send

mount -t nfs -o vers=3 xxxxxx:/data/halde /media/halde
mount.nfs: Network is unreachable

misterhsp on 10 May 2019

This is probably the same problem me and other people are also having, as described on the openwrt forum

A possible temporary fix is uninstalling latest nfs-kernel-version version and manually install older version from 17.xx.x repository, this is very easy, or you can try to compile the package yourself...

Tony-il-Capo on 11 May 2019

Am 11.05.19 um 10:55 schrieb Tony il Capo:
>

This is probably the same problem me and other people are also having,
as described on the openwrt forum
https://forum.openwrt.org/t/sudden-nfs-failure-on-18-06-2-after-package-upgrade/36289

A possible temporary fix is uninstalling latest nfs-kernel-version
version and manually install older version from 17.xx.x repository,
this is very easy, or you can try to compile the package yourself...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openwrt/packages/issues/8930#issuecomment-491493273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGJLRJLNFYYS7R65RI4OATPU2CW7ANCNFSM4HLORUYQ.

Downgrade works, thanks.

...

misterhsp on 11 May 2019

try the latest version it should fix the problem, i removed rpcbind and nfs-kernel-server now depends on portmap

tripolar on 11 May 2019

Am 11.05.19 um 18:16 schrieb tripolar:
>

try the latest version it should fix the problem, i removed rpcbind
and nfs-kernel-server now depends on portmap

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openwrt/packages/issues/8930#issuecomment-491524284,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGJLRMMYMIJUPMDAVRNHMDPU3WO5ANCNFSM4HLORUYQ.

The last version is still 2.3.3-2 in repo. Which version is the new one?

...

misterhsp on 11 May 2019

Wow. Testing on users on stable releases. What a surprise. Can you please use pull requests if possible? It would be highly appreciated if you can try it locally if it works. Now it seems that you are just blindly commiting it directly to the repository.

Also, it takes time before all targets are built. Give it a time.

BKPepe on 11 May 2019

👍1

this was the proposed change and i thought it would be a better idea to use rpcbind which broke some stuff. I tested it and it worked here. Please test it with your config and report back if it works for you

tripolar on 11 May 2019

The last version is still 2.3.3-2 in repo. Which version is the new one?

Wait for build-bot, should be there tomorrow, v2.3.3-3

Tony-il-Capo on 11 May 2019

same error with v2.3.3-3 :(

...

misterhsp on 13 May 2019

same error with v2.3.3-3 :(

Yes, I tested it this morning and same problem, downgraded again.

Tony-il-Capo on 13 May 2019

Am 13.05.19 um 16:11 schrieb Tony il Capo:
>

same error with v2.3.3-3 :(
Yes, I tested it this morning and same problem, downgraded again.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openwrt/packages/issues/8930?email_source=notifications&email_token=AKGJLRO5JP3YNYYP7HQ4DPTPVFZHNA5CNFSM4HLORUY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVIN3BY#issuecomment-491838855,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKGJLRNC7QZKKEODU6HRBHLPVFZHNANCNFSM4HLORUYQ.

Pretty stupid a not working nfs-server, I hope it is fixed soon.

misterhsp on 14 May 2019

any news?

...

misterhsp on 19 May 2019

Nope, and observing this whole situation I wouldn't count on it!..
Making changes to packages that no one or only himself tested, what the maintainer expected?! . And this is not limited to nfs-kernel-server package...

Better stick with old version for a while. Luckily it doesn't depend on specific kernel/unavailable packages... so it actually works...

Tony-il-Capo on 20 May 2019

how about providing patches? This is an open source project and not commercial support. You are free to participate.

tripolar on 20 May 2019

😕1 👎1 👍1

Any word on this. I'm dead in the water

davygrvy on 7 Jun 2019

Please see:

https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fcb41decf6c622482b20af45a77e62db8d95046e

https://forum.openwrt.org/t/nfs-broken-again/38020/24

for some (people with tiny 4MiB flash are left out) this might be fixed in the latest release.

chunkeey on 14 Jun 2019

The problem is still present under 19.0.7.0-rc1 :(

...

misterhsp on 7 Nov 2019

Chris56 on 4 Jan 2020

👍2

I've succeeded at following setting.
server(openwrt 18.06.5)
root@LEDE:~ cat /etc/exports
/mnt/sda1 *(fsid=0,rw,insecure,sync,no_subtree_check)
root@LEDE:~

client(ubuntu)
sudo /sbin/mount.nfs -v LEDE:/ /mnt/nfs_share

nakamura-takashi on 2 May 2020

👍1

I've succeeded at following setting.
server(openwrt 18.06.5)
root@LEDE:~ cat /etc/exports
/mnt/sda1 *(fsid=0,rw,insecure,sync,no_subtree_check)
root@LEDE:~

client(ubuntu)
sudo /sbin/mount.nfs -v LEDE:/ /mnt/nfs_share

I was also able to mount it that way. For me, in Arch Linux, the mount command was:

sudo /sbin/mount.nfs4 -v 192.168.0.1:/ /mnt/nfs_share