Hi,
I found this mail in my drafts folder and don't know if my thoughs are
still interesting for you, but anyway, here it is:
04.07.2007 11:40,, Maciej Bogucki wrote::
> Hello,
>
> After upgrade to bacula 2.0 sporadically I get strange error and then
> backup fail. Here is the example:
>
> --cut---
> 04-Jul 07:00 backup-sd: Please mount Volume "FILE2" on Storage Device
> "Drive-Full" (/dev/nst0) for Job file2-fd_Daily_Job.2007-07-03_23.55.00
> 04-Jul 07:01 backup-sd: Please mount Volume "FILE2" on Storage Device
> "Drive-Full" (/dev/nst0) for Job file2-fd_Daily_Job.2007-07-03_23.55.00
> 04-Jul 07:01 backup-sd: file2-fd_Daily_Job.2007-07-03_23.55.00 Fatal
> error: Too many tries: Wrong Volume mounted on device "Drive-Full"
> (/dev/nst0): Wanted FILE2 have FILE7
> 04-Jul 07:01 backup-sd: file2-fd_Daily_Job.2007-07-03_23.55.00 Fatal
> error: spool.c:281 Fatal append error on device "Drive-Full"
> (/dev/nst0): ERR=Job BackupReminderFile.2007-07-03_09.00.00 canceled
> while waiting for mount on Storage Device "Drive-Full" (/dev/nst0).
>
> 04-Jul 07:01 backup-sd: Despooling elapsed time = 01:12:40, Transfer
> rate = 12.31 M bytes/second
> 04-Jul 07:01 backup-sd: Job write elapsed time = 07:05:38, Transfer rate
> = 6.300 M bytes/second
> 04-Jul 07:01 backup-sd: file2-fd_Daily_Job.2007-07-03_23.55.00 Fatal
> error: askdir.c:320 NULL Volume name. This shouldn't happen!!!
> --cut---
>
>
> It started at 05:49, took till 07:00 to hit the "Too many tries:". It
> did this 101 times.
Well, the SD has some sort of a security measure against certain
problems. You encountered one of them: There is a hard limit to the
number of mounts until the SD cancels the running job.
> Here is my configuration of Device
As you don't have automatic mounting set up (or is there a script that
tries to mount the device?) as far as I can see, I suspect you have
the heartbeat enabled in the SD.
That's because I encountered this problem a while ago, but didn't
investigate and report a bug yet. I assume that the SD's heartbeat
wakes up the code checking for volume availability.
If that's the case, disable the heartbeat in the SD. If you've got the
FD, that heartbeat is sent to the SD and keeps the connection open
without triggering a re-check of the volume in the storage device.
Arno
> ---cut---
> Device {
> Name = Drive-Full
> Drive Index = 0
> Media Type = LTO-2
> Archive Device = /dev/nst0
> AutomaticMount = no
> AlwaysOpen = yes
> RemovableMedia = yes
> RandomAccess = no
> Maximum Spool Size = 100G
> Maximum Job Spool Size = 50G
> Spool Directory = /spool/Drive-Full
> }
> ---cut---
>
> Any ideas hot to resolve it?
>
> Best Regards
> Maciej Bogucki
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Arno Lehmann
IT-Service Lehmann
www.its-lehmann.de
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
