My wrapper script failed to write its stuff to this mornings backup. Doing a level 0 on /home/gene/Pictures, it logged this in the email:
coyote /home/gene/Pictures lev 0 partial taper: source server crc (44cff778:11146117120) and input server crc (dfd0e83a:11146117120) differ) coyote /home/gene/Pictures lev 0 was successfully retried It did leave a 10+ Gb file in the vtape, but left the failed files in the holding disk: root@coyote:~$ ls -l /sdb/dumps/20201130020105/ total 10885096 -rw------- 1 amanda amanda 2097152000 Nov 30 02:06 coyote._home_gene_Pictures.0 -rw------- 1 amanda amanda 2097152000 Nov 30 02:05 coyote._home_gene_Pictures.0.1 -rw------- 1 amanda amanda 2097152000 Nov 30 02:06 coyote._home_gene_Pictures.0.2 -rw------- 1 amanda amanda 2097152000 Nov 30 02:06 coyote._home_gene_Pictures.0.3 -rw------- 1 amanda amanda 2097152000 Nov 30 02:06 coyote._home_gene_Pictures.0.4 -rw------- 1 amanda amanda 660553728 Nov 30 02:06 coyote._home_gene_Pictures.0.5 and the error apparently causes my wrapper to exit without writing a backup copy of the database and configs for bare metal recovery to that slot in the vtapes. Effectively removing that whole backup from my ability to do a bare metal recovery. So if the main drive fails yet today, the latest I can restore to is last Saturdays run. That should be rectified by a successful run Tuesday morning but the exposure is worrying. This "crc" error has been an ongoing headache for a couple months now and with the mailing list DOA for about that same time, my previous msgs regarding this seem to have been sent to a black hole. Does anyone have a clue what its really trying to tell me? Thanks 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) 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>