There's still a pulse, but yeah I don't get the feeling that there are
more than a hundred users of amanda anymore.
I don't use xfs, but my first expectation of an amanda problem is that
it's usually permissions-related. What was the exact command you were
issuing? Is this the result of
sudo -u backup amcheckdump --verbose <config>
It would be helpful if you posted your config files.
On 2025-10-31 5:13 p.m., Hugh E Cruickshank wrote:
Hi All:
Is there anyone still on this list? I have not seen any activity for
quite some time but I am going to give it a shot anyway...
We have been using Amanda for 15+ years on six different servers but we
have now encountered something that I am not able to fix or get around.
We are setting up a new HPE DL380G11 server with an existing HPE MSL2024
tape library running RHEL9. Unfortunately amanda is no longer distributed
with RHEL so we grabbed the EPEL distribution (3.5.3). Once I got my head
around the xinet/systemd and udev/changer issues things seem to be working
well with one annoying exception. amcheckdump seems to have a problem
calling xfsrestore...
1 volume(s) needed for restoration
The following volumes are needed: DS5D1-01
Validating image fisds5:/boot dumped 20251027013001 level 0
Reading volume DS5D1-01 file 1
application stderr: /sbin/xfsrestore: usage: xfsrestore [ -a <alt. workspace
dir> ... ]
application stderr: [ -b ]
application stderr: [ -c ]
application stderr: [ -e (don't overwrite existing files) ]
application stderr: [ -f ... ]
application stderr: [ -h (help) ]
application stderr: [ -i (interactive) ]
application stderr: [ -m (force usage of minimal rmt) ]
application stderr: [ -n (restore only if newer than) ]
application stderr: [ -o (restore owner/group even if not root) ]
application stderr: [ -p ]
application stderr: [ -q ]
application stderr: [ -r (cumulative restore) ]
application stderr: [ -s ... ]
application stderr: [ -t (contents only) ]
application stderr: [ -v <verbosity {silent, verbose, trace}> ]
application stderr: [ -w (use small tree window) ]
application stderr: [ -x (try to fix rootdir due to xfsdump issue) ]
application stderr: [ -A (don't restore extended file attributes) ]
application stderr: [ -B (restore root dir owner/permissions) ]
application stderr: [ -D (restore DMAPI event settings) ]
application stderr: [ -E (don't overwrite if changed) ]
application stderr: [ -F (don't prompt) ]
application stderr: [ -I (display dump inventory) ]
application stderr: [ -J (inhibit inventory update) ]
application stderr: [ -K (force use of format 2 generation numbers) ]
application stderr: [ -L ]
application stderr: [ -O ]
application stderr: [ -Q (force interrupted session completion) ]
application stderr: [ -R (resume) ]
application stderr: [ -S ]
application stderr: [ -T (don't timeout dialogs) ]
application stderr: [ -X ... ]
application stderr: [ -Y <I/O buffer ring length> ]
application stderr: [ - (stdin) ]
application stderr: [ ]
READ SIZE: 64 kb
/sbin/xfsrestore exited with status 1
4 images not validated.
I have been doing a ton of searching but with no joy except:
Looking back at the archives for this list it appears that Bernhard
Erdmann may have encountered something similar back on December 2021:
https://mail-archive.com/[email protected]/msg51562.html
Unfortunately there were no follow up messages to his original post so
I do not know if he was ever able to resolve his issue.
Can anyone assist in at least pointing me in the right direction.
TIA
Regards, Hugh
