"John R. Jackson" wrote:
So are you saying you just did a cp of the holding disk file to the
MO disk? If so, then the MO must have a normal Unix file system on it
and the dd should have worked, assuming the cp worked. I'd start by
comparing the original and the copy, first by length (ls
Chris!
Why does if=some device work and if=some file does not? Is this
because I have an ext2 filesystem on the disk and copied the file with
cp?
If it's a file on an ext2 system, just use tar directly:
tar -xzvf the_file
OR
tar --extract --gzip --verbose --file=the_file
DL
--
The new
How do I read a file on the holding disk?
Amrestore knows how to read from the holding disk directly.
But when I copy the file to a MO-disk (2048 bytes per sector) ...
Huh? Did you copy it with the Amanda header or not?
Why does if=some device work and if=some file does not? Is this
because
"John R. Jackson" wrote:
How do I read a file on the holding disk?
Amrestore knows how to read from the holding disk directly.
I have tried
amrestore -h -p /scsi/DynaMo/linux/20001212/bacchus._usr_share.1 | dd
bs=32k skip=1 of=test.6
but test.6 seems to be neither a tar file, nor a
David Lloyd wrote:
Chris!
Why does if=some device work and if=some file does not? Is this
because I have an ext2 filesystem on the disk and copied the file with
cp?
If it's a file on an ext2 system, just use tar directly:
tar -xzvf the_file
This does not work, because the file