> I've observed similar issues in the past. A job fails part way through and 
> the catalog is not updated leaving a mismatch in the number of files in the 
> volume versus what's recorded in the catalog. This is then detected the next 
> time the volume is used, and Bacula marks the volume as Error without writing 
> anything to it.
>
> Given the mismatch, the safest thing to do is mark the volume as Full, and 
> wait for the retention period to expire so the volume can be recycled. 
> Unfortunately this wastes space (more painful when you have 100GB volumes and 
> it failed within the first few gig...), so you'll need to either have 
> sufficient spare space on your SD that you can cope with this, or be willing 
> to sacrifice the other jobs on the volume and delete jobs+purge or purge it 
> immediately to regain the space.
>
> I'm not sure how Bacula would behave if you change it straight to append; 
> whether it would leave a hole in the volume, or whether this mismatch would 
> corrupt subsequent jobs.

The times I have done this there was no problem. For file based
volumes I keep them small 5 to 10 GB and in this case it does not
really waste space to mark the volume Full and or recycling the job
with the error.

John

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users