ESG, That message simply implies that the client is unable to reach the NFS server for some reason. This could be because of a network issue or a issue on the NFS server side. What do the logs show on the server side? Also, it may be useful to check this in realtime when the issue occurs from both the client and the server to get a better assessment of the issue. - Dustin On Tue, Aug 31, 2010 at 2:07 AM, ESGLinux <esggrupos@xxxxxxxxx> wrote: > Hi all, > > I have a nfs server that I use to store my backups and in the client > machine > I get a lot of messages like these: > > Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding, > still trying > Aug 31 09:03:47 SERVER kernel: nfs: server 192.168.1.111 not responding, > still trying > Aug 31 09:03:48 SERVER kernel: nfs: server 192.168.1.111 not responding, > still trying > Aug 31 09:03:51 SERVER kernel: nfs: server 192.168.1.111 OK > > I have mounted the export this way: > > 192.168.1.111:/nas/NASDisk-00002/share on /backup type nfs > > (rw,noatime,noacl,rsize=8192,wsize=8192,hard,timeo=10,intr,addr=192.168.1.111) > > which can be the problem? Is there any problem with de mount options? > > I have tried with the soft option but with this option the server gives the > error and the backup process stops. (which is worse) > > any idea? > > Thank in advance > > ESG > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
