Hi Steve,
On Wed, Feb 12, 2003 at 04:43:19PM -0800, Steve P. Shack wrote:
> Hi,
> I'm attempting to use xfsdump to generate a dump images of a
> certain size (for backup onto cd). xfsdump claims i'm giving too many
> options. "too many -? arguments: maximum is 1 when running in
> miniroot". My command line looks something like this.
>
> xfsdump -d 750 -f backup1 -f backup2 /
>
> This seems to work on irix, or at least it doesn't bail out right
> away. irix seems to just ignore -d (but then I was testing with -d 10
> there).
>
> any ideas? I'm hoping to have xfsdump a bunch of files which I can
> write to cdr as a backup.
>
1.
You can't split up a dump to multiple files (using multiple -f's)
on Linux as we never ported this code (requires multiple threads -
needed to convert the sproc code). I don't think anyone has done
this port yet (but I noticed the xfs_copy port was done recently
which used sprocs I believe).
Since we do not allow multiple files/threads we set xfsdump to
run single threaded, which it calls "miniroot" mode - an undocumented "-z"
option used for the miniroot. That is why you got a strange error
message which was meant to be telling you that you can have only
one "-f" option.
2.
I don't think you understand the "-d" option.
It refers to the size of a "dump _media_ file".
From xfsdump(8):
"The media object records the dump stream as one or more media files.
A media file is a self-contained partial dump. The portion of a
dump stream contained on a media object can be split into several media
files. This minimizes the impact of media dropouts on the entire dump
stream, and speeds subtree restores."
And in a tape dump, there are normally multiple media files per tape.
Each media file contains at the start of it a repeat of the inode map,
directory data, etc... so that the media file within the tape can
be restored independently. Checkout cmd/xfsdump/doc/xfsdump.html
for some explanation and diagrams.
In the case of a file dump, it always uses just 1 media file.
--Tim
|