Hello,
amcheckdump does not know well xfsrestore on Linux / CentOS 7.
Two lines from
/tmp/amanda/server/be-weekly/amcheckdump.20211219163126.debug:
So Dez 19 16:31:31.502440996 2021: pid 5771: thd-0xf4c400: amcheckdump:
spawning: '/sbin/xfsrestore' '-t' '-v'
'silent'
So Dez 19 16:31
On an SGI IRIX 6.5.5m system, the following command will perform a
cumulative xfsrestore in the current directory, with verbose output.
The verbose output is useful, and is not all that verbose (as compared
to trace). The tape needs to be positioned correctly at the beginning
of the amanda dump
The header at the beginning of the amanda dump file says
to restore use
dd if=tape bs=32k skip=1 | /sbin/xfsrestore -f... -
However, this is producing errors from xfsrestore.
If you have used a dd into a piped xfsrestore under
SGI IRIX, could you email me the command?
amanda 2.4.1p1
TIA
* Anne M. Hammond ([EMAIL PROTECTED]) [20020812 18:54] thus spake:
The header at the beginning of the amanda dump file says
to restore use
dd if=tape bs=32k skip=1 | /sbin/xfsrestore -f... -
However, this is producing errors from xfsrestore.
and these would be?
If you have used a dd
Original Message
Subject: TAKE 820267 - enable xfsrestore to run on non-xfs filesystem
Date: Thu, 18 Oct 2001 13:59:49 +1000 (EST)
From: Ivan Rayner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This removes the restriction that xfsrestore -t must be run on an xfs
filesystem (which
[ XFS mailing list removed from Cc list. --JJ ]
I've patched amverify (2.4.2p2) to do the trick. It cds to /tmp/amanda
(on XFS) prior to start xfsrestore being fed by the xfsdump image: ...
Ok, it's not the nice, general, amverify.in,
testing-for-OS-and-xfsrestore solution but it works for me
Hi,
I've experienced strange filenames in Amanda's index like filename
(offset 16769536) in addition to filename for files on Linux XFS
using xfsdump-1.0.9.
The index is generated by client-src/sendbackup-dump.c:
program-backup_name = XFSDUMP;
program-restore_name = XFSRESTORE
to be the case), you need to ask
the xfsdump/xfsrestore folks.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
You're asking the wrong folks. Amanda only run xfs for you. If it's
throwing crap around (which appears to be the case), you need to ask
the xfsdump/xfsrestore folks.
I know Amanda is just my beloved, best-ever-seen and you-made-my-day
wrapper around dump/backup/xfsdump/tar...
But maybe
Ivan Rayner wrote:
On Mon, 28 May 2001, Bernhard R. Erdmann wrote:
Hi,
xfsrestore for Linux in test mode (-t) stops at the beginning if CWD is
not on a XFS filesystem:
This is a known problem in xfsrestore which has been there since day 1 in
IRIX. It has only been a minor
.
The index is generated by client-src/sendbackup-dump.c:
program-backup_name = XFSDUMP;
program-restore_name = XFSRESTORE;
indexcmd = vstralloc(XFSRESTORE,
-t,
-v, silent
Is this actually causing problems, or is it just a query as to why
you see the odd names?
Just being curious... I haven't recognized any problems yet. It just
causes an annoying listing of mangled filenames in addition to the
original filename in the index, my SysOps will ask me How can we
Is this actually causing problems, or is it just a query as to why
you see the odd names?
Just being curious... I haven't recognized any problems yet. It just
causes an annoying listing of mangled filenames in addition to the
original filename in the index, my SysOps will ask me How can
Are you using real tape media, or a file, I suspect the file case could
be smart enough not to do the split as it does not make a whole lot
of sense there.
Amanda triggers xfsdump to write to stdout while splitting it to go to
tape or a file on the holding disk (via network) and to xfsrestore
Hi,
xfsrestore for Linux in test mode (-t) stops at the beginning if CWD is
not on a XFS filesystem:
/usr/sbin/xfsrestore: ERROR: Current directory not XFS: /tmp/amanda
I consider this being a bug: no actual restore is done, so CWD's
filesystem doesn't matter.
For Amanda throwing xfsrestore
On May 28, 2001, Bernhard R. Erdmann [EMAIL PROTECTED] wrote:
/usr/sbin/xfsrestore: ERROR: Current directory not XFS: /tmp/amanda
I consider this being a bug: no actual restore is done, so CWD's
filesystem doesn't matter.
I'd go even further: xfsrestore should be capable of restoring onto
All,
I am having the same problem that Gerrit Hommersom listed in his email dated 2001,2,27. I am not a programmer, but I'll provide as much info as possible to help solve the problem.
Load tape DailySet117 now
Continue? [Y/n]: y
restore: -f argument missing
restore: usage: restore [ -a alt.
All,
I am having the same problem that Gerrit Hommersom listed in his email
dated 2001,2,27. I am not a programmer, but I'll provide as much info as
possible to help solve the problem.
Load tape DailySet117 now
Continue? [Y/n]: y
restore: -f argument missing
restore: usage: restore [ -a
I am having the same problem that Gerrit Hommersom listed in his email
dated 2001,2,27. ...
The following patch should take care of the problem:
Thanks John,
But xfsrestore still chokes.
Load tape DailySet117 now
Continue? [Y/n]: y
amrecover couldn't exec: Bad address
problem executing /sbin/xfsrestore
extract_list - child returned non-zero status: 1
Continue? [Y/n]: n
On Wednesday, March 21, 2001, at 01:32 PM, John R. Jackson
20 matches
Mail list logo
