Re: [Bacula-users] Block checksum mismatch Error during restore

[Kern S. <ke...@si...>]

On Thursday 02 June 2005 22:29, Danny Butroyd wrote:
> Matthias Vogt wrote:
> >Hi,
> >
> >I testing Bacula 1.36.0 at the moment. Everthing work fine, except the
> > restore makes waves. If I restore tape stored files I sometime get an
> > error like this
> >
> >--------------
> >DNS-and-FTP-Server: -rwxr-xr-x   1 root     root     4761012 2005-05-23
> > 08:23:33  /home/bacula-restores/opt/blackdown-jdk-1.4.
> > 2.01/jre/lib/i386/server/libjvm.so
> >basis-server-sd: RestoreFiles.2005-06-02_18.34.53 Error: block.c:304
> > Volume data error at 0:546! Block checksum mismatch in bl ock 546:
> > calc=e10b0d03 blk=243833da
> >DNS-and-FTP-Server: RestoreFiles.2005-06-02_18.34.53 Error: attribs.c:339
> > File size of restored file /home/bacula-restores/opt
> > /blackdown-jdk-1.4.2.01/jre/lib/i386/server/libjvm.so not correct.
> > Original 4761012, restored 1409024. basis-server-dir:
> > RestoreFiles.2005-06-02_18.34.53 Error: Bacula 1.36.0 (20Oct04):
> > 02-Jun-2005 18:35 JobId:                  2
> >Job:                    RestoreFiles.2005-06-02_18.34.53
> >Client:                 DNS-and-FTP-Server
> >Start time:             02-Jun-2005 18:34
> >End time:               02-Jun-2005 18:35
> >Files Expected:         247,101
> >Files Restored:         2,106
> >Bytes Restored:         34,801,378
> >Rate:                   828.6 KB/s
> >FD Errors:              1
> >FD termination status:  Error
> >SD termination status:  Error
> >Termination:            *** Restore Error ***
> >
> >-------------
> >
> >I use a HP StorageWorks Ultrium 460 Tape Drive (LTO-2). I've read that
> > this error is maybe caused by an damage tape drive or tape. Is that true?
> > I have tested different tapes and the error somtimes still appears deping
> > on amount of data or whatever.
>
> I have had this problem before and i too thought at first it was dodgy
> media/drive/scsi card, however, the problem "went away" when I upgraded
> to the latest version of bacula (currently 1.36.3).  I also use and
> LTO-2 tape libraray (Overland Powerloader) but im not sure that this has
> anything to do with the issue :)

The most likely source of this kind of error is a bad tape or possibly bad 
RAM.  It would be *really* hard for Bacula to create a block checksum error 
because of a bug.  I can believe that the problem went away when you 
upgraded, but it was most likely because you changed tapes.

-- 
Best regards,

Kern

  (">
  /\
  V_V