You are doing a dump to tape and the taper failed.
The dumper close the socket to the client, and the client detect the
socket is close.
The first error is the taper. sendbackup error is the result of the
taper error.
Jean-Louis
Stefan G. Weichinger wrote:
Some infos from the client-side:
--->
sendbackup: start: server:data_db lev 0
sendbackup: time 0.092: spawning /bin/gzip in pipeline
sendbackup: time 0.092: argument list: /bin/gzip --fast
sendbackup-gnutar: time 0.092: pid 29494: /bin/gzip --fast
sendbackup-gnutar: time 0.092: doing level 0 dump as
listed-incremental to
'/usr/local/var/amanda/gnutar-lists/serverdata_db_0.new'
sendbackup-gnutar: time 0.099: doing level 0 dump from date:
1970-01-01 0:00:00 GMT
sendbackup: time 0.108: spawning /usr/local/libexec/runtar in pipeline
sendbackup: time 0.108: argument list: runtar daily gtar --create
--file - --directory /data/db --one-file-system --listed-incremental
/usr/local/var/amanda/gnutar-lists/serverdata_db_0.new --sparse
--ignore-failed-read --totals .
sendbackup-gnutar: time 0.109: /usr/local/libexec/runtar: pid 29497
sendbackup: time 0.109: started backup
sendbackup: time 0.109: started index creator: "/bin/gtar -tf -
2>/dev/null | sed -e 's/^\.//'"
sendbackup: time 11140.170: index tee cannot write [Broken pipe]
sendbackup: time 11140.214: pid 29495 finish time Thu May 29 05:53:19
2008
Seems as if the index-creation fails, correct?
But why would it then say
taper: retrying server:data_db.0 on new tape due to: [writing file: No
space left on device]
??
hmm
Stefan
