[opensuse] Suddenly, broken NFS ownership on client side

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Using NFS on 11.4 both server and client. Today I see this - I changed nothing - on the client:

minas-tirith:~ # l /var/cache/zypp/nfs_packages/11_4/
total 12
drwxr-xr-x 29 4294967294 4294967294 4096 Jun 29 00:23 ./
drwxr-xr-x 6 4294967294 4294967294 4096 Feb 12 03:01 ../
- -rw-r--r-- 1 4294967294 4294967294 0 Jun 3 2011 11.4
drwxr-xr-x 3 4294967294 4294967294 19 Mar 24 01:36 EXT.P_NVidia/
drwxr-xr-x 5 4294967294 4294967294 52 May 9 2011 Ext_Packman/
drwxr-xr-x 2 4294967294 4294967294 6 May 9 2011 Ext_Videolan/
drwxr-xr-x 2 4294967294 4294967294 4096 Jun 9 15:16 Ext_google-talkplugin/


The same directory on the server side:

Telcontar:~ # l /var/cache/zypp/packages.link/
total 12
drwxr-xr-x 29 root root 4096 Jun 29 00:23 ./
drwxr-xr-x 6 root root 4096 Feb 12 03:01 ../
- -rw-r--r-- 1 root root 0 Jun 3 2011 11.4
drwxr-xr-x 3 root root 19 Mar 24 01:36 EXT.P_NVidia/
drwxr-xr-x 5 root root 52 May 9 2011 Ext_Packman/
drwxr-xr-x 2 root root 6 May 9 2011 Ext_Videolan/
drwxr-xr-x 2 root root 4096 Jun 9 15:16 Ext_google-talkplugin/


What happened to the users name? It should be root, not that number.


/etc/exports (server):

/data/storage_c/repositorios_zypp/ 192.168.1.0/24(fsid=1234,rw,no_root_squash,nohide,no_subtree_check,insecure)


/etc/fstab (client):

192.168.1.14:/data/storage_c/repositorios_zypp/ /var/cache/zypp/nfs_packages nfs defaults,noauto,nofail 0 0


- -- Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAk/s3JUACgkQtTMYHG2NR9UzEwCgixB+5IS5qdcLV9LbBSx/TCsU
8yYAoJP+G6ViDPA738LEq+i2KLkJY3of
=hhop
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

Relevant Pages

  • Errors writing large files via NFS
    ... files larger than a certain size to a NFS server. ... client systems, although the definition of "too large" varies. ... network paths involved, I'm pretty sure we're not seeing a network problem. ...
    (Tru64-UNIX-Managers)
  • Re: Still getting NFS client locking up
    ... > the same NFS lockups. ... > Reading from the server works perfectly all the time. ... > NFS CLIENT: ... in particular, look at traces for any client blocked in NFS, ...
    (freebsd-current)
  • Re: Bugs in mkfs.xfs, device mapper, xfs, and /dev/ram
    ... it gets the first ENOSPC error back from the server at around 1.5GB ... the data that gets ENOSPC errors is ... I'm no great expert but isn't this a design flaw in NFS? ... corruption because the NFS client thinks it has written the data ...
    (Linux-Kernel)
  • Re: [OT] Real time systems, was: Re: What is the draw of VMS?
    ... your nfs clients are going to hang. ... You can tell NFS to do soft mounts, if you find this acceptable, but the cost is data corruption. ... probing the server and running the highest level available. ... My client programs gets stuck until the server is back. ...
    (comp.os.vms)
  • Re: Problems mounting nfs from freebsd to Mac.
    ... Problems mounting nfs from freebsd to Mac. ... I've got an nfs server that's refusing to mount one client - via one ... That elimintes NFS on the client, and -most- of the NFS config on the ...
    (freebsd-questions)