by : Hi,
: One of our postgrads has a corrupted Exabyte tape which he desperately
: needs to read.
: gtar with '-i' has retrieved most of the data, but eventually gives up
: with 'I/O Error: Too Many Errors'.
: I think (hope) that only part of the tape is corrupted.
You may want to play with the hardware blocking factors on the tape.
You can set the block size to whatever you want. By default it's
variable blocking. But if the tape was created with a specific blocking
that didn't agree with gtar's blocking, you could get interesting
situations indeed. Might be worth checking what the setup was on the
machine that created the tape.
If I recall correctly Exabytes always write in multiples of 8K, (amount
of data per stripe) regardless of what your blocking is. For that
reason here, I have gtar write to the exabyte tapes using a blocking
factor of 16 instead of the default 20.
: Shaun McCullagh,
: IT Support Officer,
: School of Information Systems.,
: University of East Anglia.,
: Norwich
: England NR4 7TJ
: Office: E02.109
: *******************************************************************
: Life is like sanskrit read to a pony
: *******************************************************************
--
Physics Dept # 403 492 5728 mornings (Math Dept)
University of Alberta # 3713 afternoons 0714 Fax
Edmonton, AB, T6G 2J1 # Contract Unix system admin & troubleshooting