Re: [Bacula-users] [Non-DoD Source] Re: Bacula kills tape drive and autoloader

2017-07-26 Thread Darold Lucus
lsscsi -L This will list your auto changer mtx -f /dev/sgx status This will list all of the tapes in your auto changer. root@nas:~# mtx -f /dev/sg1 status Storage Changer /dev/sg1:1 Drives, 16 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=13100

Re: [Bacula-users] [Non-DoD Source] Re: Bacula kills tape drive and autoloader

2017-07-26 Thread Ana Emília M . Arruda
Hello Daniel, Did you run the btape tests? were the tests successful? All tapes need to be blank tapes before you label them in Bacula. If, for example, you use tar to write to the tape, then you label this tape in Bacula, only the space not used by the tar command will be available to be used by

Re: [Bacula-users] [Non-DoD Source] Re: Bacula kills tape drive and autoloader

2017-07-26 Thread Hicks, Daniel CTR OSD DMEA
Ana Thanks for your help, your suggestions helped to get me started. I also needed to define within the source pool that is was a read pool for the job. Now I have two different issues, one where I can only write a small amount of data about 2GB of data and then the tape is marked full,

Re: [Bacula-users] [Non-DoD Source] Re: Bacula kills tape drive and autoloader

2017-07-24 Thread Ana Emília M . Arruda
Hello Daniel, You are welcome :-). I see you are using /dev/sgX and /dev/nstX device names for the autochanger configuration. This is not recommended since they can be modified after server reboots. Please use /dev/tape/by-id values or even udev rules. Also, I noticed you have a pool configured

Re: [Bacula-users] [Non-DoD Source] Re: Bacula kills tape drive and autoloader

2017-07-24 Thread Hicks, Daniel CTR OSD DMEA
Thanks for the reply Ana. Here is most of the info you asked. I will work on running btape again but now it is just timing out and saying that the device cannot be accessed when I try to run the fill test. [root@server ~]# lsscsi -g [0:2:0:0]diskLSI MR9260-8i2.13 /