From: Winston Sorfleet Sent: November 5, 2025 17:16
>
> Hugh, I don't see xfsdump invoked at all, it should be going to your
> LTO based on what I see and assuming that /dev/changer isn't some weird
> link to something other than the scsi symbolic for the robot. Do you
> have something weird in your advanced.conf, dumptypes, or tapetypes?
> Can you do a grep xfs in the directory?
Hi Winston:
The amcheckdump does not do a dump it only checks a previous amdump run.
We use it as sort of a verification step. Out backup scripts generally
look like:
:
/usr/sbin/amdump WeeklySet1
/usr/sbin/amcheckdump WeeklySet1
The amdump writes the tape and the amcheckdump reads & verifies the tape.
As per the man page:
Amcheckdump verifies Amanda dump images by reading them from storage
volume(s) and verifying that the images can be parsed by the
appropriate application (if available). For example, a GNUTAR image
is passed to GNU Tar for parsing, and any errors (e.g., corrupt or
missing data) are noted.
At this point I am only assuming the amdump is writing a valid tape but I
do not know for sure. I am going to try to extract the images on the tape
and confirm that they have been written as xfsdump or tar format, as
appropriate. If there are xfsdump images then I will know amdump worked
correctly and amcheckdump did not. If there are no xfsdump images then I
will know amdump did not work correctly.
Regards, Hugh
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
