On Sat, Oct 10, 2020 at 19:20:25 -0400, Chris Hoogendyk wrote:
> The taper log from last night looks exactly like the amcheck log,
> showing the same inventory followed by the updating state and the
> same three repetitions of the warning at line 102.
So you are saying that the taper log from last night goes up through the
lines that look like
> Thu Oct 08 23:30:04.244060162 2020: pid 18920: thd-0x28b4800: taper: mtx:
> Storage Element 48:Full :VolumeTag=CLN002CU
> Thu Oct 08 23:30:04.244209614 2020: pid 18920: thd-0x28b4800: taper:
> NEO200x48: updating state
, then switch to the warning lines from oldest.pm line 102, and then
aborts suddenly?
It's not getting you an actual solution, but I'm curious if changing to
a different taperscan algorithm in the amanda.conf file (or using
-otaperscan= , if you have any other ones defined already) allow
"amcheck -s" to complete sucessfully (and in any case what the amcheck
log file looks like with the another taperscan algorithm)....
Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
