Version 1.34.4 is pretty old, and there were some seg faults in btape when 
attempting two volume fill tests in btape.  I'd recommend that you move up to 
version 1.36.3 at the least, and since you are just starting to setup Bacula, 
you might want to try the Beta version 1.37.30.  

You shouldn't be getting SCSI errors, though.  They might be related to the 
seg fault, but I doubt it.  Perhaps you are running with an older version of 
mtx, which is known to be somewhat buggy.

On Tuesday 02 August 2005 11:27, John Huss wrote:
> Hello all,
>
> I've been attempting to set Bacula up on a Gentoo Linux system. (Bacula
> version 1.34.4) I have been following the documentation, specifically
> the section entitled: 'Tape Testing'.
>
> I have run the btape command and done 'test' which ran successfully on
> my drive and tape changer. For reference it is a:
>
> bacula # cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 05 Lun: 00
>   Vendor: QUANTUM  Model: ValueLoader      Rev: U11r
>   Type:   Medium Changer                   ANSI SCSI revision: 02
> Host: scsi0 Channel: 00 Id: 06 Lun: 00
>   Vendor: HP       Model: Ultrium 2-SCSI   Rev: F78V
>   Type:   Sequential-Access                ANSI SCSI revision: 03
>
>
> And have run the ' btape -c bacula-sd.conf /dev/st0 ; fill' but got some
> errors:
>
> Wrote blk_block=3275000, dev_blk_num=5000 VolBytes=211,276,700,873
> rate=24589.9 KB/s
> Wrote blk_block=3280000, dev_blk_num=32 VolBytes=211,599,260,817
> rate=24593.1 KB/s
> Wrote blk_block=3285000, dev_blk_num=5032 VolBytes=211,921,820,769
> rate=24596.3 KB/s
> Flush block, write EOF
> btape: btape Error: Write error at 431:1 on device /dev/st0. ERR=No
> space left on device.
> btape: Re-read of last block succeeded.
> btape: btape.c:2165 Last block at: 431:0 this_dev_block_num=1
> btape: btape.c:2198 End of tape. VolumeCapacity=211,921,949,793. Write
> rate = 24556.4 KB/s
> btape: End of medium on Volume "TestVolume1" Bytes=211,921,949,793
> Blocks=3,285,001 at 01-Aug-2005 18:56.
> btape: 3301 Issuing autochanger "loaded drive 0" command.
> btape: 3302 Autochanger "loaded drive 0", result is Slot 1.
> btape: 3303 Issuing autochanger "unload slot 1, drive 0" command.
> Unloading Data Transfer Element into Storage Element 1...done
> btape: 3304 Issuing autochanger "load slot 2, drive 0" command.
> btape: 3305 Autochanger "load slot 2, drive 0", status is OK.
> Wrote Volume label for volume "TestVolume2".
> btape: 3301 Issuing autochanger "loaded drive 0" command.
> btape: 3302 Autochanger "loaded drive 0", result is Slot 2.
> btape: Wrote label to prelabeled Volume "TestVolume2" on device
> "/dev/st0"
> btape: New volume "TestVolume2" mounted on device /dev/st0 at
> 01-Aug-2005 18:58.
> Done writing ...
> Wrote End Of Session label.
> Wrote state file last_block_num1=0 last_block_num2=11
>
>
> Done filling tapes. Now beginning re-read of first tape ...
> btape: 3301 Issuing autochanger "loaded drive 0" command.
> btape: 3302 Autochanger "loaded drive 0", result is Slot 2.
> btape: Fatal Error because: Bacula interrupted by signal 11:
> Segmentation violation
> Kaboom! btape, btape got signal 11. Attempting traceback.
> Calling: /btraceback /btape 0
> execv: /btraceback failed: ERR=No such file or directory
> Traceback complete, attempting cleanup ...
> Orphaned buffer:  100016 bytes allocated at line 1745 of btape btape.c
> Orphaned buffer:      80 bytes allocated at line 131 of btape block.c
> Orphaned buffer:   64528 bytes allocated at line 135 of btape block.c
> Orphaned buffer:      80 bytes allocated at line 131 of btape block.c
> Orphaned buffer:   64528 bytes allocated at line 135 of btape block.c
> Orphaned buffer:      80 bytes allocated at line 131 of btape block.c
> Orphaned buffer:   64528 bytes allocated at line 135 of btape block.c
> Orphaned buffer:      80 bytes allocated at line 106 of btape block.c
> Orphaned buffer:   64528 bytes allocated at line 118 of btape block.c
>
> Any ideas? I do see some scsi errors in dmesg, do you think this is the
> cause of the problem? (scsi errors below)
>
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command
> opcode:opcode=0x4D.
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x5.
> 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command
> opcode:opcode=0x34.
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command
> opcode:opcode=0x4D.
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command opcode:opcode=0x5.
> 3w-9xxx: scsi1: ERROR: (0x03:0x010D): Invalid field in CDB:.
> 3w-9xxx: scsi1: ERROR: (0x03:0x0101): Invalid command
> opcode:opcode=0x34.
>
> I've never setup a tape drive before so please forgive me if I'm being
> stupid.
>
> Regards,
>
>
>
> Johnny
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
Best regards,

Kern

  (">
  /\
  V_V


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to