[Bacula-users] DDS-4 restore error

[JML <jm...@le...>]

Hello again,

I have a separate issue with restoring from a DDS-4 changer (specifically
a Sony TSL-S11000). System is RedHat 9. Changer ops and backup work fine,
then I get the following during a restore job:

nail-sd: Ready to read from volume "foo-06" on device /dev/nst0.
nail-sd: Forward spacing to file:block 0:1.
nail-sd: RestoreFiles.2004-02-12_16.36.23 Error: block.c:248 Expected 
block-id BB01 or BB02, got . Buffer discarded.
nail-sd: RestoreFiles.2004-02-12_16.36.23 Error: block.c:248 Expected 
block-id BB01 or BB02, got . Buffer discarded.
nail-sd: RestoreFiles.2004-02-12_16.36.23 Error: Read error on Record 
Header /dev/nst0: Success
nail-fd: RestoreFiles.2004-02-12_16.36.23 Error: bnet.c:374 Write error 
sending to Storage daemon:nail:9103: ERR=Broken pipe
nail-dir: RestoreFiles.2004-02-12_16.36.23 Error: Bacula 1.33 (30Jan04): 
12-Feb-2004 16:38
JobId:                  35
Job:                    RestoreFiles.2004-02-12_16.36.23
Client:                 nail-fd
Start time:             12-Feb-2004 16:36
End time:               12-Feb-2004 16:38
Files Restored:         0
Bytes Restored:         0
Rate:                   0.0 KB/s
FD Errors:              1
FD termination status:  Error
SD termination status:  Error
Termination:            *** Restore Error ***

Seems to make no difference whether I "mark *" or only restore a subset of
the job. I also followed the instructions pertaining to mt stoptions.

btape's test gives a clean bill of health on this drive, though after
advising that I set the last two options in my Device declaration below:

Device {
  Name = DDS-4                        # 
  Media Type = DDS-4
  Archive Device = /dev/nst0
  Autochanger = Yes
  Changer Command = "/usr/local/bacula/etc/mtx-changer %c %o %S %a"
  Changer Device = /dev/sg1
  LabelMedia = No
  AutomaticMount = yes;               # when device opened, read it
  AlwaysOpen = yes;
  Fast Forward Space File = no
  Backward Space Record = No
}



All of this sounds similar to a thread from last week when the advice was
to upgrade to 1.32f-4, which had fast block rejection disabled. Is this
disabled already in the 1.33 beta, or is there an easy way to do so?

best,

Jason