I upgraded nfs-utils last night, but i didnt work the way I expected it. AFAIR
pacman found a file /var/lib/nfs/state which "...already exists" I stopped nfs,
I rebooted the computer even without nfs in rc.conf, the problem remained.
pacman -U didnt work either. Furthermore, pacman -R nfs-utils didn't remove
the file. Finally, I removed it manually and reinstalled the new version.
Any suggestions what happened?
My guess is that whoever did the update realized that this state file would be created, if it didn't exist, so they added it to the package... then again, I could be wrong.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Hm, I just cleaned up my pkg-cache only a couple of minutes ago. There have been two or three previous packages in there. I feel Murphy is around...
nfs-utils 1.0.4 decided to include the state file on install, rather than create it at runtime.
This isn't a show-stopping conflict. You can safely --force it.
here is one more problem I have with nfs. I don't know what it is actually
related to - the new version or my limited knowledge - so her it goes:
I connect my laptop from time to time to my mainbox via nfs.
portmap: 192.168.0.3, 192.168.0.5, 192.168.0.7
nfsd: 192.168.0.3, 192.168.0.5, 192.168.0.7
nfslock: 192.168.0.3, 192.168.0.5, 192.168.0.7
lockd: 192.168.0.3, 192.168.0.5, 192.168.0.7
rquotad: 192.168.0.3, 192.168.0.5, 192.168.0.7
mountd: 192.168.0.3, 192.168.0.5, 192.168.0.7
statd: 192.168.0.3, 192.168.0.5, 192.168.0.7
mount: 192.168.0.3, 192.168.0.5, 192.168.0.7
umount: 192.168.0.3, 192.168.0.5, 192.168.0.7
roadrunner:/usr/abs /mnt/lap_abs nfs noauto,user 0 0
roadrunner:/home/keep /mnt/lap_keep nfs noauto,user 0 0
roadrunner:/var/cache/pacman /mnt/lap_cache nfs noauto,user 0 0
everything was fine until the update, now I can mount one of the
mount-points and thats it. I can umount it with an error:
UMNT RPC: RPC: cannot receive
It is impossible to remount it, or mount a second filesystem.
now the real strange thing: If I restart the nfs-server and work then on the
client I still can work in the previously mounted system and can mount
one new system. This can be repeated until all systems are
After all, I think it is rather a problem with configuration but I don't have
any ideas where to start. I not the real nfs crack, Really not. Does
anybody know how I can repair that?