Re: Problem with tar on boot disk
2002-08-30 10:18:46
On Fri, Aug 30, 2002 at 10:55:04AM +0200, Luc Dewavrin wrote:
> Hello,
>
> I have setup Amanda server ( 2.4.2-p2) on Redhat Linux 7.2 with
> 10 Amanda clients running on Redhat 5.1 -> 7.2.
> Backups and restores with Amanda utilities work really fine.
> Backups are tar compressed on client side;
>
> I have tried a "bare level" restoration from a boot disk using
> this command:
> # scp -n mybackupserver ' amrestore -p /dev/ntape 192.168.0.100 /boot' |
> tar -xvf -
>
> Amanda finds the archive on the tape and writes it to standard output.
> The standard output is piped to my local tar program.
> The problem is that tar extraction creates a lot of unexepected directories
> like
> "072315522404" or "07345503322" ... in which i can find the content of my
> tar file.
>
> I supposed that it is because the tar program on my boot disk is not a Gnu
> tar.
> The boot disk i use is tomrstbt and i have also tried with Redhat 7.2 rescue
> disk
> => same problem.
>
> Is it a known issue ? Any idea how i could fix it?
In a very limited sample (one) I had a tape created by a bad gnutar version.
Reading back with the same tar gave results similar to yours.
I had a good gnutar version available and that was able to read the tape.
Perhaps you could be so luckey that installing a good gnutar version will
let you recover cleanly.
--
Jon H. LaBadie jon AT jgcomp DOT com
JG Computing
4455 Province Line Road (609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
|
|