You are not logged in.

#1 2014-06-29 00:30:49

GeneArch
Member
Registered: 2013-07-28
Posts: 78

New NFS problem with symbolic links

Posted to arch-general as well.

I 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 internal mirror of arch repo - so testing.db is a symbolic link to test.db.tar,gz)

# ls -l testing.db testing.db.tar.gz
ls: cannot read symbolic link testing.db: Input/output error
0 lrwxrwxrwx 1 root root    17 Jun 28 14:12 testing.db
16 -rw-rw-r-- 1 root root 14204 Jun 28 14:12 testing.db.tar.gz


On server:
# ls -l testing.db testing.db.tar.gz
lrwxrwxrwx 1 root root    17 Jun 28 14:12 testing.db -> testing.db.tar.gz
-rw-rw-r-- 1 root root 14204 Jun 28 14:12 testing.db.tar.gz


  One more piece of info:

    If on the client - I create a new symbolic link - it is totally 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 ...

    # ls -l JUNK testing.db
lrwxrwxrwx 1 root root 17 Jun 28 20:24 JUNK -> testing.db.tar.gz
lrwxrwxrwx 1 root root 17 Jun 28 14:12 testing.db -> testing.db.tar.gz

But any links created on server are broken on clients.

Offline

#2 2014-06-29 00:55:57

GeneArch
Member
Registered: 2013-07-28
Posts: 78

Re: New NFS problem with symbolic links

Following up :

  Rebooted server a second time (previously clients were rebooted first) - and now all clients are happy.

Offline

Board footer

Powered by FluxBB