Yes, that did the trick. I changed the setting on my NFS server; "retrieve(wait)" processing attribute so the server waits for the recall to finish before it sends the response back to the client.
Thanks! -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Saturday, September 09, 2006 6:57 PM To: [email protected] Subject: Re: Bacula question; Make sure you specify on the z/OS NFS server that the server providing the filesystem is to wait synchronously for recalls to complete before returning. There is no timer in Bacula that measures that response if the server does not return a "wait" message; you're seeing the server respond with a "not available, wait a few" message that the NFS client doesn't understand. Bacula retries when it gets that message, and eventually gives up. See the z/OS NFS feature manual for the parm to specify synchronous response (don't have manuals here). David Boyes Sine Nomine Associates ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
