Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+backups\s+fail\s+with\s+\"ERR\=Stale\s+NFS\s+file\s+handle\"\,\s+but\s+NFS\s+is\s+not\s+in\s+use\!\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+backups\s+fail\s+with\s+\"ERR\=Stale\s+NFS\s+file\s+handle\"\,\s+but\s+NFS\s+is\s+not\s+in\s+use\!\s*$/: 2 ]

Total 2 documents matching your query.

1. [Bacula-users] backups fail with "ERR=Stale NFS file handle", but NFS is not in use! (score: 1): Author: mark.bergman AT uphs.upenn DOT edu; Date: Wed, 02 Nov 2011 11:07:14 -0400; Last night I had two long-running backup jobs (~1TB and ~1.2TB) fail with the same error: Fatal error: Error writing data to spool file. ERR=Stale NFS file handle The problem is that the spool file i; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-11/msg00004.html (16,737 bytes)
2. Re: [Bacula-users] backups fail with "ERR=Stale NFS file handle", but NFS is not in use! (score: 1): Author: Martin Simmons <martin AT lispworks DOT com>; Date: Fri, 4 Nov 2011 20:54:28 GMT; "Stale NFS file handle" is the error code ESTALE and usually means that the nfs server was rebooted. Maybe GPFS gives it a similar meaning? __Martin -- RSA(R) Conference 2012 Save $700 by Nov 18 Reg; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-11/msg00044.html (12,342 bytes)

Current List: 1 - 2
Page: [1]