I tried to dump my filesystem with following command: xfsdump -f /dosc/dimage / After 640 seconds was dump interrupted with advice to resume it by -R option. But it doesn't work, xfsdump says that media contains valid xfsdump but does not support append. I used this command: xfsdump -R -f /dosc/dimage /
hello,
Apologies for the slow response. I've reassigned this bug to
the xfsdump package (not xfsprogs) and have had a discussion
with one of the guys who knows alot about xfsdump internals.
It seems that what you are trying to do may not be supported by
xfsdump. Since xfsdump was originally written as a dump-to-tape
program rather than a dump-to-file program, some of its error
messages are non-obvious, and behavior with regular files is,
IMHO, suboptimal. In your case, the message "media doesn't
support append" apparently is because (quoting one of the
xfsdump folks)..
"Basically, in drive_simple.c there is no DRIVE_CAP_APPEND
capability set for the drive type. (drive_scsi.c is the
only one that handles append, it seems.)"
He goes on to say:
"I think he needs to specify a new file to resume the dump...
(Actually that's really just a guess -- you should run a test
to confirm.)"
So, I tried it out and found that you can indeed resume a dump
to file by specifying a different file name. There's a gotcha,
however, in that xfsdump will only resume on "dump media file"
boundaries (see -d option) - and for files, there is (AFAICT)
only one "media file" in the dump - the actual file. Since we
don't get through completing that one "media file" during the
interupted dump, xfsdump has to restart the "media file" (thus
defeating the point of resuming!) ... I'm not sure if it is
possible to workaround this by using the -d option somehow.
If you want to try this out, you will probably be helped by
the xfsinvutil(8) tool - this shows which dumps (and partial
dumps) are related, which were interupted, etc..
I will mention these issues to the xfsdump maintainers and see
whether they have anything more to add or if they can fix this,
but I wouldn't hold my breath.
cheers.
Hello Resume of dump is second level problem. First is timer which after 640 seconds interrupts xfsdump and in case of output file ends dumping. I didn't find anything about that timer in xfsdump manpage. Solution would be to add another option to xfsdump to cancel or change the timer. Jan
Hello I found reason of interruption of the dump process. I used for dumpfile fat32 and xfsdump met with 2GB limitation. So additional info from xfsdump would be helpful. Jan
hi Jan, Can you mail the full output from your failing dump to me please? That way I can get a better idea of what is in need of correcting wrt additional info. thanks.
Yes. Output: -------------------------------------------------- xfsdump: using file dump (drive_simple) strategy xfsdump: version 3.0 - Running single-threaded xfsdump: WARNING: most recent level 0 dump was interrupted, but not resuming that dump since resume (-R) option not specified xfsdump: level 0 dump of pisidlo:/ xfsdump: dump date: Mon Sep 16 18:13:11 2002 xfsdump: session id: 0cbe682f-5f26-4370-9b22-d025c6c5b75e xfsdump: session label: "session" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: skipping (no pruning necessary) xfsdump: ino map phase 4: skipping (size estimated in phase 2) xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 3845600384 bytes xfsdump: creating dump session media file 0 (media 0, file 0) xfsdump: dumping ino map xfsdump: dumping directories xfsdump: dumping non-directory files xfsdump: ending media file xfsdump: media file size 2147483647 bytes xfsdump: dump size (non-dir files) : 2104763392 bytes xfsdump: NOTE: dump interrupted: 643 seconds elapsed: may resume later using -R option xfsdump: Dump Status: INTERRUPT -------------------------------------------------- Size of dumpfile is 2147483647 bytes.