Hello List,

i am having a problem with a new bacula system i have set-up. After 
running for a while, bacula reportet a Media Error on the Medium and 
marked the medium as Faulty. To finish the Job, it requested 
intervention (insert a new Medium and labeling).

Inserting a blank Medium and trying to Label it, produces the following 
Error:

Connecting to Storage daemon TapeStorage at bacula.....:9103 ...
Sending label command for Volume "20080604" Slot 0 ...
3910 Unable to open device "TapeStorage" (/dev/tape/by-id/scsi-1-nst): 
ERR=dev.c:433 Unable to open device "TapeStorage" 
(/dev/tape/by-id/scsi-1-nst): ERR=Read-only file system

Label command failed for Volume 20080604.
Do not forget to mount the drive!!!

The device worked fine for a couple of days, so i think the 
configuration should be ok. The really strange thing is, that it is a 
new tape. Inserting a different Tape produces normal output from mt (BOT 
WR ONLINE etc), but inserting the tape that bacula tried to label 
produces the following:

SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x42 (LTO-2).
Soft error count since last status=0
General status bits on (45010000):
 BOT WR_PROT ONLINE IM_REP_EN

The Medium was OK before bacula tried to label it, but now the drive 
sets the WR_PROT flag as soon as the medium is inserted.

What does bacula do to the tape that i cant even "mt erase" them? Does 
Bacula do something to a Tape Volume that has a write error except 
marking it faulty internally? I have had exactly the same problems using 
the btape "fill" command to test filling the drive, bacula labeled tapes 
were marked WR_PROT until i used a different tape to reset that flag, 
and using the scsi erase command to clear the tape.

I have to admit that i am fairly new to tape backups, so maybe i am 
missing something really obvious, but writing to tape via TAR, cpio, dd 
and combinations of that, never resulted in tapes that were marked 
WR_PROT, unless i set the hardware switch on the LTO 2 medium... I am 
really stumped as to what i should do, since i expect that now and then 
a medium will fail, and getting bacula back to a usable state after that 
has taken me over 2 hours alone today.. i dont think that should be normal.

Device {
  Name = TapeStorage
  Media Type = Tape
  Archive Device = /dev/tape/by-id/scsi-1-nst
  AutomaticMount = yes;               # when device opened, read it
  AlwaysOpen = yes;
  RemovableMedia = yes;
  RandomAccess = no;
  LabelMedia = yes;                   # lets Bacula label unlabeled media
  Spool Directory = /data/lto/spool/ ;
  Maximum Spool Size = 140 GB ;
  Maximum Network Buffer Size = 65536 ;
  Volume Poll Interval = 15 min ;
}

bacula-sd Device section for the tapedrive which is a Tandberg LTO2 HH 
in case it matters. Only thing changed is the Archive Device, since it 
contains the serial number of the tape.

If someone has a working (Tandberg) LTO2 configuration, i would be glad 
for any tipps, but so far it has worked OK since switching to bacula. 
Has anyone had that strange error of bacula-sd marking media as WR_PROT? 
Is it even an error, or is it normal and i am just misinterpreting it?

Thank you for the time

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users