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?

On 2025-11-05 19:35, Hugh E Cruickshank wrote:
From: Behalf Of Winston Sorfleet Sent: October 31, 2025 16:39
There's still a pulse, but yeah I don't get the feeling that there are
more than a hundred users of amanda anymore.
Hi Winston:

Thanks for your response.

I don't use xfs, but my first expectation of an amanda problem is that
it's usually permissions-related.
This is always a good call but, in this case, the xfsrestore command is
being found and executed but it objecting the parameters on the command
line.

What was the exact command you were issuing?  Is this the result of
sudo -u backup amcheckdump --verbose <config>
I have not been able to determine what the amcheckdump xfsretore command
looks like but when I run:

     amcheckdump WeeklySet1

I get the same results that are in the amcheckdump generated email.

It would be helpful if you posted your config files.
Here is the amanda.conf file contemnts:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
org "WeeklySet1"              # your organization name for reports
dumpuser "amandabackup"       # the user to run dumps under
mailto"[email protected]"    # space separated list of operators at your site
dumpcycle 0 week                # the number of days in the normal dump cycle
runspercycle 1          # the number of amdump runs in dumpcycle days
autoflush    on         # flush the dumps from holding disk to tape

define changer my_robot {
     tpchanger "chg-robot:/dev/changer"
     property "tape-device" "0=/dev/nst0"
     property "use-slots" "6-10"
}
dtimeout 1800   # number of idle seconds before a dump is aborted
ctimeout 30     # max number of secconds amcheck waits for each client
etimeout 300    # number of seconds per filesystem for estimates
define dumptype global {
        comment "Global definitions"
        auth "bsdtcp"
}
define dumptype gui-base {
        global
        program "GNUTAR"
        comment "gui base dumptype dumped with tar"
        compress none
        index yes
}
define dumptype excl-tar {
        global
        program "GNUTAR"
        comment "user partitions dumped with tar"
        compress none
        index    yes
        priority medium
        exclude list "/etc/amanda/WeeklySet1/excllist"
}

define policy WeeklySet1 {
     retention-tapes   4
     retention-days    0
     retention-recover 0
     retention-full    0
}

define storage WeeklySet1 {
     policy "WeeklySet1"      # the policy
     tapepool "WeeklySet1"    # the tape-pool
     tpchanger "my_robot"     # the changer
     runtapes 1         # number of tapes to be used in a single run of amdump
     tapetype "HP-LTO6"       # what kind of tape it is
     labelstr "^DS5W1-[0-9][0-9]*$"   # label constraint regex: all tapes must 
match
     #autolabel
     #meta-autolabel
     taperscan "traditional"
     #max-dle-volume 1000000
     #taperalgo first
     #taper-parallel-write 1
}
storage "WeeklySet1"

define tapetype HP-LTO6 {
     comment "Created by amtapetype; compression disabled"
     length 2442818016 kbytes
     filemark 256 kbytes
     speed 89467 kps
     blocksize 32 kbytes
}

holdingdisk hd1 {
     directory "/u10/tmp/hd1"
     use 100 gb
     chunksize 1 mbyte
}

includefile "advanced.conf"
includefile "/etc/amanda/template.d/dumptypes"
includefile "/etc/amanda/template.d/tapetypes"
Thanks, Hugh

Reply via email to