search for: nfs0

...readlink that gives the error. I'm not sure why readlink is used in this case. This is a regular file and not a symlink. I hope you have some suggestions on how to debug this further. Details on the servers's file systems: Server backupserver: /data is mounted like this: nfs:/data/nfs/nfs0/data/xx/backup on /data type nfs (rw,timeo=60,intr,rsize=16384,wsize=16384,addr=78.xx.xx.xx) Server mailserver: /data is mounted like this: nfs:/data/nfs/nfs0/data/xx/mail on /data type nfs (rw,timeo=60,intr,rsize=16384,wsize=16384,addr=78.xx.xx.xx) Med venlig hilsen/Kind regards Thomas Damgaar...

...commonly accepted way of dealing with this that doesn't involve making all our host names unique? Bonus question: We have 2 storage servers (let's call them storage0 and storage1), and between them they run a floating IP address with a heartbeat-monitored NFS daemon (let's call that nfs0). Now, obviously the host key changes whenever there's been a failover, and so again we get this same kind of problem. What to do in this case? Any ideas? Thank you all for your time. -- Med venlig hilsen Christian Iversen

Hi, When I try to execute the following: smbclient -U% -L localhost I receive the following error: tdb(/usr/local/samba/var/locks/gencache.tdb): expand_file write of 1024 failed (Invalid argument) [2003/10/26 19:45:58, 0] lib/util_sock.c:read_socket_with_timeout(279) read_socket_with_timeout: timeout read. read error = Broken pipe. protocol negotiation failed Any ideas anyone? I have