I'm running Amanda 2.6.0p2 on Linux and am using Amazon's S3 to store all of my backup data. However periodically I entounter an error similar to: *snip some log*
driver: result time 23.589 from taper: TAPER-OK driver: send-cmd time 23.589 to taper: FILE-WRITE 00-00001 /backup/holding/20080909203001/lithium._chroot.0 lithium /chroot 0 20080909203001 0 driver: startaflush: FIRST lithium /chroot 740 25600000 driver: state time 23.589 free kps: 600 space: 48787456 taper: writing idle-dumpers: 4 qlen tapeq: 4 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 23.589 if default: free 600 driver: hdisk-state time 23.589 hdisk 0: free 48787456 dumpers 0 driver: state time 23.590 free kps: 600 space: 48787456 taper: writing idle-dumpers: 4 qlen tapeq: 4 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 23.590 if default: free 600 driver: hdisk-state time 23.590 hdisk 0: free 48787456 dumpers 0 driver: result time 23.590 from taper: REQUEST-NEW-TAPE 00-00001 driver: send-cmd time 23.590 to taper: NEW-TAPE While listing S3 keys: CURL error: Failed writing body (CURLcode 23) taper: Error writing label BUCKETNAME012 to device BUCKETNAME012/. taper: using label `BUCKETNAME012' date `20080910075725' These last 3 lines repeat. The only workaround that I have found is to destroy the bucket, rename it and relabel it and re-run amflush. I would much rather prefer to find a more proper fix to this bug; has anyone come across this before and is there a fix/workaround? -- Regards, -Lisa http://www.crudvision.com
