Mailinglist Archive: opensuse-factory (577 mails)

< Previous Next >
[opensuse-factory] Tumbleweed update to 20200201 destroyed nfs/nfs-server
I have five local Tumbleweed machine that can no longer utilize nfs nor
nfs-server since the movement of /etc/services & company to /usr/

No changes have been made to firewall since nfs was working, but disabling
firewall does not enable nfs connection(s).

Have temporarily converted nearly everything to sshfs.

I can access nfs exports from a server running a locked down 42.2.
<correction> I *could* ...

<more> yast nfs while adding another export from a newly
installed Tw reports it cannot access 2 nfs shares from the 42.2 server.
BUT I can access those shares. I cannot access the nfs share from the new
Tw box.

will reboot desktop,, and see if any nfs shares survive.


The shares from the 42.2 server survived, including the ones yast reported
broken but the new share from the new Tw did not mount and I cannot mount

So another attempt to add an nfs share from the new Tw (
yast reports:
new share failed (show parameters)
mount.nfs: No route to host
exit code

Mounting at /mnt/nfs/crash2-paka
Unexpected situation found in the system.
Click below to see more details (English only).
Continue despite the error?

command '/bin/mount -t nfs ''
mount.nfs: No route to host
exit code:

said to continue despite error:

nfs share mount was added to /etc/fstab
manual attempt to mount from
mount.nfs: trying text-based options
mount.nfs: mount(2): No route to host

attempts to share from provide similar results

I have no idea where to go next to trouble-shoot this issue.

(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri openSUSE Community Member facebook/ptilopteri
Photos: paka @ IRCnet freenode
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups