Re: no space left on Bacula server

I think the problem was 3 large full backup jobs of the same client 
running on the same day.

The reason for that was a very high transmission error rate on the 
network interface for that client slowing down transfers to a crawl. 
Subsequently fixed.

JobId 4133
Backup Canceled
Fatal error: Max run sched time exceeded. Job canceled.

JobId 4139
Backup failed -- Incomplete

JobId 4140
Backup OK -- with warnings
Error: Error writing header to spool file. Disk probably full. 
Attempting recovery. Wanted to write=64512 got=32772

I definitely did not start the last 2 simultaneously.
Either one was added automatically or I canceled the first one manually 
and it did not cancel as expected. Can't remember for sure, was dealing 
with many things at once.

I'm now hoping that "Backup OK -- with warnings" actually has all the 
data and appending incremental ones will work without issues.