Dear DUGURUs,
Yesterday, I began to tar up four big Oracle .dbf files two 1GB files and one 2GB file. After it sat there for
two minutes, I decided - " The hell with this!" and was going to use individual compresses on the dbf files.
I did a ^c to kill the tar. Well, it seems that the first dbf file in my tar list was suddenly 130MB instead of
1 GB. The killing of the tar truncated the dbf file!!
The particulars:
AlphaServer 2100 4/200 running 4.0b DU.
Firmware: 5.0
Anybody know why this happens?
I never expected that an input file would be corrupted.
There is a patch for 4.0b for a tar (pax) problem, but it sounds like it creates a
corrupted tar file, not a source file.
Thanks In Advance!
Wayne Sweatt
Received on Thu Nov 20 1997 - 18:31:01 NZDT