Hi,
https://doc.bareos.org/master/html/bareos-manual-main-reference.html is
not reachable, so I try to find help on the mailing list.
I see strange JobSpoolSize Values in an Job-Output:
backup-sd-muc User specified Job spool size reached:
JobSpoolSize=618,666,912 MaxJobSpoolSize=429,496,729,600
Writing spooled data to Volume. Despooling 618,666,912 bytes ...
backup-sd-muc Despooling elapsed time = 00:00:04, Transfer rate = 154.6
M Bytes/second
MaxJobSpoolSize is right, because I defined
"Maximum Job Spool Size = 400g" in the device-entry of bareos-sd.
The Maximum Spool Size is set to 800g.
Where came the value of 618666912 from? It's 590.0067 MB!
Another failed job, shows that the spool-dir is perhaps full:
##############################################################################
Error: Error writing header to spool file. Disk probably full.
Attempting recovery. Wanted to write=-1 got=12
Writing spooled data to Volume. Despooling 64,524 bytes ...
Fatal error: Error writing header to spool file. ERR=No space left on device
fileserver--fd Fatal error: backup.c:1019 Network send error to SD.
ERR=Connection reset by peer
##############################################################################
But the spool-disk should be large enough:
Filesystem Size Used Avail Use% Mounted on
/dev/sdf1 1.8T 68M 1.7T 1% /var/bareos/spool
All backuped data from this day is <500GB.
The bareos-sd host is different from the bareos-dir host, but I think
not that this can be a reason for this.
Any hint's
Udo
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
