More problems - could really use some help on this one.
Rebooted the server today after full update (testing) - now ALL nfs
clients get Input/Output error on any symbolic link - regular files are
fine.
Server/client both:
nfs-utils 1.3.0-2
rpcbind 0.2.1-5
On any client (this is an
One more piece of info:
If on the client - I create a new symbolic link - it is fine on
both client and server.
On Client:
# ln -s testing.db.tar.gz JUNK
# ls -l JUNK
0 lrwxrwxrwx 1 root root 17 Jun 28 20:24 JUNK - testing.db.tar.gz
Same back on the NFS server ...
#
Rebooted server a second time (prev clients were rebooted first) -
and now all clients are happy.
Odd no?
Am Sat, 21 Jun 2014 08:59:30 +0200
schrieb Andreas Radke andy...@archlinux.org:
Am Fri, 20 Jun 2014 16:48:21 -0400
schrieb Genes Lists li...@sapience.com:
This is probably unlikely but I'll ask. Is it possible that
something that nfs needed (but missing from systemd service file)
had
Am Sun, 22 Jun 2014 09:49:29 +0200
schrieb Andreas Radke andy...@archlinux.org:
But this shouldn't be necessary because nfs-server.service has:
grep rpcbind /usr/lib/systemd/system/nfs-server.service
Requires= network.target proc-fs-nfsd.mount
After= network.target proc-fs-nfsd.mount
Am 22.06.2014 09:57, schrieb Andreas Radke:
Am Sun, 22 Jun 2014 09:49:29 +0200
schrieb Andreas Radke andy...@archlinux.org:
But this shouldn't be necessary because nfs-server.service has:
grep rpcbind /usr/lib/systemd/system/nfs-server.service
Requires= network.target proc-fs-nfsd.mount
Am Fri, 20 Jun 2014 16:48:21 -0400
schrieb Genes Lists li...@sapience.com:
This is probably unlikely but I'll ask. Is it possible that something
that nfs needed (but missing from systemd service file) had not
actually come up yet but several minutes later it was up and then nfs
was able to
On 06/18/2014 09:17 AM, Tobias Powalowski wrote:
After running this update - my nfs server won't run at all - I get this
error:
systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
Active: failed
On 06/20/2014 04:16 PM, Genes Lists wrote:
...
..rpc.nfsd[872]: rpc.nfsd: writing fd to kernel failed: errno 11(...ed)
More strangeness - after a while I tried loading all the pieces by
hand - and suprisingly that worked. Then after that, the systemd
nfs-server service works if re-started
This is probably unlikely but I'll ask. Is it possible that something
that nfs needed (but missing from systemd service file) had not actually
come up yet but several minutes later it was up and then nfs was able to
start?
Thought I'd ask.
gene/
10 matches
Mail list logo