I've noticed a strange behavior with "Maximum Volume Jobs" parameter.
I've set it to 3 at the volume initialization.
For the following backup on this volume, i change the parameter to 5
(because I have 3 new servers to backup)
after few time i have this error :
05-sep 15:18 vel-bck-1-sd: papi-mgc-002-backup.2007-09-05_00.01.05 Error:
Re-read of last block OK, but block numbers differ. Last block=62775 Current
block=62777.
and the volume become "Full" (he's not really full but bacula close him)
The only way to pass through this problem is to delete the volume in catalog
and erase completely the tape (with mt). mt -f /dev/tape weof isn't
sufficient
why this behavior ?
I think the Maximum Volume Jobs information is also stored on the tape (in
the volume himself) so tape needs to be erase for working back
have anyone noticed that?
Thanks
Noran
-------------------------------------------------------------------------
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
