Re: [Bacula-users] Autochanger Problem: Second label is not being mounted

[<mar...@up...>]

In the message dated: Tue, 31 Jan 2012 18:50:07 -0200,
The pithy ruminations from Isamar Maia on 
<Re: [Bacula-users] Autochanger Problem: Second label is not being mounted> wer
e:
=> 2012/1/31  <mar...@up...>:
=> > In the message dated: Tue, 31 Jan 2012 17:14:24 -0200,
=> > The pithy ruminations from Isamar Maia on
=> > <[Bacula-users] Autochanger Problem: Second label is not being mounted> were:
=> > => Hi Folks,
=> > =>
=> > => We are using a HP 1x8 G2 AutoLDR Autochanger with Bacula version 5.2.3
=> > =>
=> > => We're facing the following problem:
=> > =>
=> > => 1) When I restart Bacula and run a Daily backup job, it automatically
=> > => mounts the first tape, labeled as "KDZ000L4"(tape1)
=> > => and it works perfectly well.
=> > =>
=> > => 2)  In the sequence, when it's necessary to load a second
=> > => tape(KDZ003L4), the tape is physically loaded into the drive but
=> > => Bacula stucks
=> > => with the following message:
=> >
=> > Was that tape already labeled?
=> 
=> Yes. I can see them with "list volumes".


Well, that says that a volume with that name was added to the database,
not that the tape itself was physically labled...but it's unlikely that
the tape was not labeled at the time it was added.

Do you use "label barcodes" to add new media?

=> 
=> And "mtx -f /dev/changer status" says:
=> 
=> mtx -f /dev/changer status
=>   Storage Changer /dev/changer:1 Drives, 8 Slots ( 0 Import/Export )
=> Data Transfer Element 0:Full (Storage Element 8 Loaded):VolumeTag =
=> KDZ003L4
=>       Storage Element 1:Empty
=>       Storage Element 2:Empty
=>       Storage Element 3:Empty
=>       Storage Element 4:Empty
=>       Storage Element 5:Full :VolumeTag=KDZ000L4
=>       Storage Element 6:Full :VolumeTag=KDZ001L4
=>       Storage Element 7:Full :VolumeTag=KDZ002L4
=>       Storage Element 8:Empty
=> 
=> I imported them into Bacula using "update volumes".

Do you mean:
	update volumes
then
	slots from autochanger

That tells bacula to update it's idea of what tapes are present, but I
don't believe that it writes a label to any tape.

		
=> Also, "list volumes" lists them OK.
=> 
=> 
=> 
=> 
=> >
=> > Was that tape used before?
=> >

	[SNIP!]

=> 
=> One problem here.. when running "readlabel", an error comes out:
=> 
=> Tape block granularity is 1024 bytes.
=> btape: butil.c:290 Using device: "/dev/nst0" for writing.
=> 31-Jan 18:44 btape JobId 0: 3301 Issuing autochanger "loaded? drive 0" command.
=> 31-Jan 18:44 btape JobId 0: 3302 Autochanger "loaded? drive 0", result
=> is Slot 8.
=> btape: btape.c:477 open device "Fita" (/dev/nst0): OK
=> *readlabel
=> 31-Jan 18:45 btape JobId 0: Error:
=> btape: btape.c:526 Volume has no label.


That's the same symptom that I am having--the label gets corrupted and
bacula can no longer use the tape.

Unfortunately, we have not determined an exact cause, and do not have a
solution.

Mark

=> 
=> 
=> 
=> >
=> > The problem sounds very similar to what I described previously. See the
=> > list archive for the subject "critical error -- tape labels get corrupted,
=> > previous backups unreadable":
=> >
=> >        http://sourceforge.net/mailarchive/message.php?msg_id=28718589
=> >
=> > Mark
=> >
=> > =>
=> > => What should be the problem ?
=> > =>
=> > => Isamar
=> > =>
=> > =>
=> > => --
=> > => Isamar Maia
=> > => Cel. VIVO SSA:  (55) 71-9146-8575
=> > => Cel. TIM SSA: (55) 71-9185-5264
=> > => Fixo:  (55) 71-4062-8688
=> > => $BF|K\(B: +81-(0)3-4550-1212
=> > => Skype ID: isamar.maia
=> > =>
=> 
=> 
=> 
=> -- 
=> Isamar Maia
=> Cel. VIVO SSA:  (55) 71-9146-8575
=> Cel. TIM SSA: (55) 71-9185-5264
=> Fixo:  (55) 71-4062-8688
=> $BF|K\(B: +81-(0)3-4550-1212
=> Skype ID: isamar.maia
=>