Is anyone on the list using Bacula and have configured it? I keep getting the same ol' error no matter what .. utility:/etc/bacula # rm /backups/bacula/backups/archive ; btape -c /etc/bacula/bacula-sd.conf /backups/bacula/backups/archive Tape block granularity is 1024 bytes. btape: butil.c:258 Using device: "/backups/bacula/backups" for writing. btape: btape.c:335 open_dev /backups/bacula/backups OK *test === Write, rewind, and re-read test === I'm going to write 1000 records and an EOF then write 1000 records and an EOF, then rewind, and re-read the data to verify that it is correct. This is an *essential* feature ... btape: btape.c:786 Wrote 1000 blocks of 64412 bytes. btape: btape.c:465 Wrote 1 EOF to /backups/bacula/backups btape: btape.c:802 Wrote 1000 blocks of 64412 bytes. btape: btape.c:465 Wrote 1 EOF to /backups/bacula/backups btape: btape.c:811 Rewind OK. 1000 blocks re-read correctly. 1000 blocks re-read correctly. === Test Succeeded. End Write, rewind, and re-read test === === Write, rewind, and position test === I'm going to write 1000 records and an EOF then write 1000 records and an EOF, then rewind, and position to a few blocks and verify that it is correct. This is an *essential* feature ... btape: btape.c:898 Wrote 1000 blocks of 64412 bytes. btape: btape.c:465 Wrote 1 EOF to /backups/bacula/backups btape: btape.c:914 Wrote 1000 blocks of 64412 bytes. btape: btape.c:465 Wrote 1 EOF to /backups/bacula/backups btape: btape.c:923 Rewind OK. Reposition to file:block 0:4 26-Feb 18:35 btape: btape Error: block.c:264 Volume data error at 0:4! Wanted ID: "BB02", got "". Buffer discarded. btape: btape.c:979 Read block 5 failed! file=0 blk=4. ERR=Input/output error btape: btape.c:989 This may be because the tape drive block size is not set to variable blocking as normally used by Bacula. Please see the Tape Testing chapter in the manual and look for using mt with defblksize and setoptions If your tape drive block size is correct, then perhaps your SCSI driver is *really* stupid and does not correctly report the file:block after a FSF. In this case try setting: Fast Forward Space File = no in your Device resource.