Re: Failed with strange errors
2006-09-28 00:58:02
On Sep 27, 2006, at 12:15 PM, JB Segal wrote:
Sadly, it's not that easy: (I'm a totally different person having the
same problem.
-sh-3.00$ amcheck smarterliving
Amanda Tape Server Host Check
-----------------------------
WARNING: holding disk /backup/smarterliving: only 57203900 kB free
(73400320 kB requested)
slot 12: read label `SL00018', date `20060918'
NOTE: skipping tape-writable test
Tape SL00018 label ok
Server check took 24.834 seconds
Amanda Backup Client Hosts Check
--------------------------------
Client check: 19 hosts checked in 10.243 seconds, 0 problems found
(brought to you by Amanda 2.5.1)
while my nightly amdump does the same thing Nick's does (and Olivier
Nicole, Steven Backus and a bunch of others:
These dumps were to tapes SL00016, SL00017.
The next 3 tapes Amanda expects to use are: SL00018, SL00019, SL00002.
The next new tape already labelled is: SL000138.
FAILURE AND STRANGE DUMP SUMMARY:
central /home lev 1 FAILED [cannot read header: got 0
instead of 32768]
mattapan /data1 lev 1 FAILED [cannot read header: got 0
instead of 32768]
chinatown /boot lev 1 FAILED [cannot read header: got 0
instead of 32768]
central /home lev 1 FAILED [cannot read header: got 0
instead of 32768]
central /home lev 1 FAILED [too many dumper retry:
"[request failed: timeout waiting for ACK]"]
mattapan /data1 lev 1 FAILED [too many dumper retry:
"[request failed: timeout waiting for ACK]"]
mattapan /data1 lev 1 FAILED [cannot read header: got 0
instead of 32768]
haymarket / lev 1 FAILED [cannot read header: got 0
instead of 32768]
chinatown / lev 1 FAILED [cannot read header: got 0
instead of 32768]
haymarket / lev 1 FAILED [too many dumper retry:
"[request failed: timeout waiting for ACK]"]
chinatown /boot lev 1 was successfully retried
chinatown / lev 1 was successfully retried
Just to add a "metoo", I'm suddenly getting these same errors.
I was getting these before upgrading to 2.5.1 and assumed it was a
tar incompatibility. After upgrading, and starting a new backup
series the errors stopped. Now, suddenly, they've started up again.
Any ideas of what to look for to correct this?
Thanks,
Bruce.
|
|
|