After looking at the amenda sources and the command you found, there appears to
be a missing argument to the xfsrestore command. The missing argument is a
single trailing '-', which specifies that xfsrestore reads from stdin. I
suspect that either this functionality was never tested/used or that the
xfsrestore command on Linux has changed. The place that this needs to be added
is in perl/Amanda/Extract.pm. There are two lines where xfsrestore arguments
are specified:
"XFSDUMP" => [ $Amanda::Constants::XFSRESTORE, qw(-v silent) ],
"XFSDUMP" => [ $Amanda::Constants::XFSRESTORE, qw(-t -v silent) ],
I'm pretty sure the lines should be:
"XFSDUMP" => [ $Amanda::Constants::XFSRESTORE, qw(-v silent -) ],
"XFSDUMP" => [ $Amanda::Constants::XFSRESTORE, qw(-t -v silent -) ],
You can probably edit the perl file in your installation tree to test to see if
this corrects the amcheckdump behavior.
I don't know if anybody who has the ability to commit changes to Amanda is
paying attention to this list, but if they are, maybe this fix will get applied.
Pieter
________________________________________
From: [email protected] <[email protected]> on behalf
of Hugh E Cruickshank <[email protected]>
Sent: Thursday, November 6, 2025 2:39 PM
To: 'Amanda Users List'
Subject: RE: amcheckdump xfsrestore errors
From: Hugh E Cruickshank Sent: November 6, 2025 13:31
>
> Here is what I found:
>
> spawning: '/sbin/xfsrestore' '-t' '-v' 'silent'
>
> and
>
> info: /sbin/xfsrestore exited with status 1
I missed a few lines:
/sbin/xfsrestore: ERROR: no source file(s) specified
/sbin/xfsrestore: usage: xfsrestore [ -a <alt. workspace dir> ... ]
It is looking more and more like the problem is internal to the
amcheckdump command.
Regards, Hugh
--
Hugh E Cruickshank, Forward Software, www.forward-software.com
