Hi, I'm running Bareos 15.2.3 on centos 6.
configured 60G spool size, but seems like bareos actually uses 1M and 2M spoolsize. I'm not able to find a pattern, but also seen 7M and 8M spoolsizes. here are the messages from logs: 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Spooling data ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Forward spacing Volume "Incr-3618" to file:block 0:220. 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: User specified Device spool size reached: DevSpoolSize=60,020,128,434 MaxDevSpoolSize=60,000,000,000 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Writing spooled data to Volume. Despooling 1,048,588 bytes ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Despooling elapsed time = 00:00:01, Transfer rate = 1.048 M Bytes/second 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Spooling data again ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: User specified Device spool size reached: DevSpoolSize=60,021,177,022 MaxDevSpoolSize=60,000,000,000 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Writing spooled data to Volume. Despooling 2,097,176 bytes ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Despooling elapsed time = 00:00:02, Transfer rate = 1.048 M Bytes/second 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Spooling data again ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: User specified Device spool size reached: DevSpoolSize=60,021,177,022 MaxDevSpoolSize=60,000,000,000 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Writing spooled data to Volume. Despooling 2,097,176 bytes ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Despooling elapsed time = 00:00:01, Transfer rate = 2.097 M Bytes/second 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Spooling data again ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: User specified Device spool size reached: DevSpoolSize=60,021,177,022 MaxDevSpoolSize=60,000,000,000 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Writing spooled data to Volume. Despooling 2,097,176 bytes ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Despooling elapsed time = 00:00:01, Transfer rate = 2.097 M Bytes/second Some of the jobs fail after a while with the following errors: 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Spooling data again ... 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: End of Volume at file 0 on device "DiskDeviceIncr1" (/data/bareos-storage/Incr), Volume "Incr-3618" 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Ready to read from volume "Incr-3621" on device "DiskDeviceIncr1" (/data/bareos-storage/Incr). 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Forward spacing Volume "Incr-3621" to file:block 0:999959905. 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Error: block.c:286 Volume data error at 0:999959905! Wanted ID: "BB02", got " al". Buffer discarded. 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Fatal error: mac.c:636 Fatal append error on device "DriveDevice" (/dev/nst0): ERR= 28-Dec 08:19 muc1pro-backup-1-sd JobId 9648: Elapsed time=00:00:14, Transfer rate=20.81 M Bytes/second 28-Dec 08:19 muc1pro-backup-1-dir JobId 9648: Error: bsock_tcp.c:422 Write error sending 371 bytes to Storage daemon:muc1pro-backup-1.adm.financial.com:9103: ERR=Broken pipe Before setting the spoolsize to 60GB, it was 512GB and didn't see behavior/erros like these. the spooling process was either filling up to 512G oder up to job size if less than 512GB. Any clues why the spooling doesn't work correctly? Thank you. Robert -- 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.
