On Thursday 21 October 2021 12:05:05 William Morder via tde-users wrote:
We can't
see the full headers in the archive, or at least I can't
see any way to access them, but in my copy, it also seems to have no
mystery header.
I believe that whatever caused the problem, poking at it with a
stick has caused it to go away.
I declare the problem fixed, until it reoccurs :-)
Here is something else to
throw a little K2 in to fire.
copy/pasted from a msg I just posted to the amanda list. It may have a
bearing on this:
From: Gene Heskett <gheskett(a)shentel.net>
To: amanda-users(a)amanda.org
On Thursday 21 October 2021 10:09:19 Gene Heskett wrote:
Finally, the answer to my many backup failures that
actually explains
it.
<https://www.truenas.com/community/resources/list-of-known-smr-drives.
141/>
Here is another link with good info and a better explanation of the tech.
<https://blocksandfiles.com/2020/04/15/seagate-2-4-and-8tb-barracuda-and-desktop-hdd-smr/>
I can only imagine that I might have used an old
template by mistake,
and maybe that contained the problematic reference lines.
This will be a long post.
8 or 10 months ago I had a hell of a time with amanda, I was useing a
perfectly good 1Tbyte baracuda as a holding disk, used by amanda to
collect data from client machines so writeing to tape wasn't constricted
by the src bandwidth which will shoeshine the tape drive if its not fed
data tast enough.
But I also use vtapes, not physical ones so shoeshining the tape is not a
concern here.
But I kept getting CRC errors for the holding disk files, so amanda would
redo that disklist entry again, (and again) until it got a good crc.
Desparate to find a solution I pulled the data cable off the 1T seagate
baracuda and plugged in a 240gig samsung evo 860 SSD I'd originally
bought to make a raid6 or 10 /home drive out of. Never done as I now
have assembled a 4 pack of 1Tbyte samsung evo 870's for that.
I'm using amanda to back up the goodie parts of 5 other machines in
addition to this one and was used to a 20 gigabte backup taking 3 or 4
hours in the night. But putting in the SSD, I was amazed that this same
sized backup was now taking 20 minutes, and my errors were GONE!
There are places where an SMR drive is ok, write once, read mostly is ok,
but as a fast in, faster out buffer for amanda sure isn't one of them.
So if you have a multi user situation, and servicing this mailing list
surely fits in that box, using an SMR drive could very well bite us in
the ass with exactly this sort of fantom problems. The write speed for
files bigger than the drives buffer can stretch to minutes and requires
help from the device driver that the drive may not convey to the driver
that it needs help.
While trying to track down the problem, however, I did
some
housecleaning, and got rid of the old stuff that I never (or at least
thought I never) use any more. So if it was in an old template, it's
gone now.
Let's hope this is the end of it. Thanks everybody for their patience.
Now I am trying to get Konversation to run over Tor using their onion
links. I haven't had time to get the IRC going.
Bill
Take care all.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/gene>