On Dec 18, 1:01pm, Stephen Manley wrote:

Subject: Re: 5.x Restore cannot read 4.x dumps

...

Below is a dialog with our F630 running 5.1.2P1 trying to read a tape

written

...

with 4.x. We were able to recover data from this tape using a filer

running

...

4.3R4D2.

range> restore tvf rst0l RESTORE: Tape Block size should be 10240, not 64512. Fri Dec 18 13:00:12 EST [isp_main]: Tape block was shorter than byte count.

Requested = 4096, Read = -50176

...

RESTORE: Could not initialize media. range> restore tvfb rst0l 64512 RESTORE: No buffers available.

...

We figured people would get bitten by this change, so we added the error message (which is obviously not effective) RESTORE: Tape Block size should be x, not y.

Now, how do I know the error message didn't work?

This message didn't work because it is not obvious.

I'd recommend changing the message to somthing like:

RESTORE: restore defaulted to a tape block size of 63K RESTORE: your dump was written with a tape block size of 10K RESTORE: re-trying the restore with the block size of 10K

... and then doing the restore with the blocksize that is on the tape.

Since you could print the message, you have all the information needed to do The Right Thing (tm) on the users behalf.

If I'm doing a restore, it's usually to recover from a disaster. When I'm recovering from a disaster, people are anxious for their data, I'm tired, frustrated and not in the mood to deal with balky restore software.

-Skottie