Re: [Dump-users] Resuming a verify after transient hardware failure

[Kenneth P. <sh...@se...>]

--On Saturday, September 06, 2008 10:50 PM +0200 Stelian Pop 
<st...@po...> wrote:

> What do you mean by "resume" ? Did restore crashed, or stopped with some
> error, and you want to launch it again and compare _the rest_ of the
> data ?

I'm running it from cron and see this in the log mailed to me:

decompression error, block 31241281: data error
File decompression error while restoring ./srv/dav/prealign/data2.zip
continue? [yn] Dump   date: Sun Sep  7 01:17:06 2008

> Normaly, if the bad block is inside an inode data, restore should signal
> the error, and ask you if you want to continue (unless you did specify
> -y, in which case it does this automatically).

I wasn't using -y. Will that retry the block?

> If the bad block happens to be at the place some important metadata was
> saved, well, I guess bad things can happen...

I suspect the block is fine and there's some glitch in the USB HD driver. 
(I'm also asking on the CentOS list to see if anyone's heard of such an 
issue. The failing block number is very suspicious.)