Sergey Poznyakoff wrote:
> [EMAIL PROTECTED]:/
> > 10 # tar vx -M $(seq -f"--file=/mnt/backup/v%g.tar" -s" " 146 148)
> > home/share/D60/725CANON/CRW_2526.CRW
> > tar: home/share/D60/725CANON/CRW_2526.CRW: Cannot extract -- file
> > is continued from another volume
> This means that this file starts on one of the previous archives. Try
> decreasing the archive number (145, 144,...) to find out the exact
> location.
>
> Regards,
> Sergey
Humm. I see that my message was not sufficiently clear to explain what
is going on. In the case of the previous example the file CRW_2526.CRW
does reside on the boundry between archive 145 and 146 but I would like
tar to skip that file and begin extracting with the next one. After
examing the output in my message perhaps you are misinterpreting the
verbose output from tar as part of the command line? No file is
specified for extraction on the command line, that's part of the output.
Humm... I wonder what would happen if I did specify a file, the next
file that is; with the -K option...
[EMAIL PROTECTED]:/home/scratch
26 # tar vx -M -B $(seq -f"--file=/mnt/backup/v%g.tar" -s" " 146 148)
\ -K home/share/D60/725CANON/CRW_2527.CRW
home/share/D60/725CANON/CRW_2526.CRW
tar: home/share/D60/725CANON/CRW_2526.CRW: Cannot extract -- file is
continued from another volume
tar: Skipping to next header
tar: home/share/D60/725CANON/CRW_2527.CRW: Not found in archive
tar: Error exit delayed from previous errors
[EMAIL PROTECTED]:/home/scratch
27 #
That did not work.
Do you think that my use of the POSIX format for multi-volume archives
might be causing problems? I had to throw the posix flag to tar because
the gnu format couldn't (can't?) handle long file paths in multi-volume
archives.
-Sam
_______________________________________________
help-tar mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-tar
