Hi Lars,
You wrote on 10 Jul 2002:
> XFS version: SGI_XFS_1.0.2
> Tape Drive: Tandberg SLR100
> ...
> I am using XFS since version 1.0 and I am quite satisfied. I have one
> peeve, that xfsdump/restore are a bit too complicated to use: It seems
> impossible to restore a tape that I have copied file by file
> to a harddisk without tweaking the source to xfsrestore. xfsrestore also
> aborts with an assertion failure when I try to restore directly from
> the tape.
1. I don't believe that xfsdump/restore is too complicated to use.
It has an awful lot of options (I agree) but there are examples
on what ones are needed to get a basic dump and restore happening:
check out the examples sections in:
- cmd/xfsdump/doc/README.xfsdump
- xfsdump(8) and xfsrestore(8) man pages
2. xfsdump uses different formats for dumping to a tape than
dumping to a file. A tape dump format has multiple media files
(mini self contained dumps) and tape record headers, which provide
redundant information in order to provide better chances for restoring
stuff when only part of a tape has errors on it
(I believe that's the idea anyway).
So one is not supposed to copy a dump from tape onto a disk file and
then restore it. After the "strategy" type (tape or file format)
is chosen, it checks on restore to make sure the dump is of the correct
matching strategy.
3. I don't know why xfsrestore is aborting with an assertion failure for you.
You'll need to post:
- the output from "mt status"
- the command line used for xfsrestore
- final verbose output from xfsrestore (e.g. -v5)
- the actual assert message
Some possibilites:
- Some tape drives can be considered like QIC tape drives
(check output from "mt status") and need the -q option.
- There have been some fixes for asserts in recent times so it may
be of use to get the latest xfsdump/restore from CVS.
(Check out cmd/xfsdump/doc/CHANGES for info)
Please post to linux-xfs@xxxxxxxxxxx for xfsdump queries.
Cheers,
--Tim
|