Bacula-users

Re: [Bacula-users] Device is BLOCKED when one tape is marked with error

2008-09-14 11:07:51
Subject: Re: [Bacula-users] Device is BLOCKED when one tape is marked with error
From: "Jose Ildefonso Camargo Tolosa" <ildefonso.camargo AT gmail DOT com>
To: "Jeronimo Zucco" <jczucco AT ucs DOT br>
Date: Mon, 15 Sep 2008 10:37:37 +1930
Hi!

I got this same problem, but there were no more available tapes on
that pool (well, just one more, there were just two tapes) ....
furthermore, I noticed that the tape's slots were mixed up (I guess it
was my mistake, the tapes have not barcodes, and maybe I unloaded the
tapes to the wrong slot last time I did some manual movement, or maybe
It wasn't me, I'm not sure).  Anyway, it went like this:

I got Vol00001 and Vol00002, for some reason Vol00001 went to "error"
state, and it tried to mount Vol00002, but due to the "slots mixup",
it actually mounted Vol00001 again (duh...), I tried to manually mount
Vol00002, it actually read it, and then it automatically mounted
Vol00001 again (it didn't updated the slot... should it?, I was
mounting it using bconsole's mount command).  I'm sure it was Vol00002
there because the autochanger got two drives, and I mounted that slot
(slot 2, actually) to the *other* drive, and it read the label
correctly and stated it got Vol00002, so, I went and umounted it, then
tried to mount to the "active" drive, it mounted it, and just unload
it and mount Vol00001 again.  So, I canceled the job.

This is a new bacula installation, so I just went ahead and purged
Vol00001 volume, removed Vol00002, manually removed its label (using
dd).... and labeled a few new tapes (Vol00003 (the old Vol00002), and
Vol00004).  At this point, I found that Vol00001's slot were not
correct, so I updated its info.  This far it has filled two tapes (and
ran 5 backup jobs) with no problem... so, I guess the whole issue was
the slot number problem.

I have never had this problem with another installation were I use bar
code labels, whenever I move a tape, the db just updates correctly.


Anyway, I got some of the logged errors here:

09-Sep 21:30 bacula-dir JobId 16: Start Backup JobId 16,
Job=server-shared.2008-09-09_21.30.08
09-Sep 21:30 bacula-dir JobId 16: Using Device "ULT3-1"
09-Sep 21:30 servernt-fd JobId 16: DIR and FD clocks differ by 9
seconds, FD automatically compensating.
09-Sep 21:30 bacula-sd JobId 16: 3307 Issuing autochanger "unload slot
2, drive 1" command.
09-Sep 21:30 bacula-sd JobId 16: 3304 Issuing autochanger "load slot
1, drive 1" command.
09-Sep 21:31 bacula-sd JobId 16: 3305 Autochanger "load slot 1, drive
1", status is OK.
09-Sep 21:31 bacula-sd JobId 16: Volume "Vol00001" previously written,
moving to end of data.
09-Sep 21:51 bacula-sd JobId 16: Error: Unable to position to end of
data on device "ULT3-1" (/dev/nst1): ERR=dev.c:895 ioctl MTEOM error
on
+"ULT3-1" (/dev/nst1). ERR=Input/output error.

09-Sep 21:51 bacula-sd JobId 16: Marking Volume "Vol00001" in Error in Catalog.
09-Sep 21:51 bacula-sd JobId 16: 3307 Issuing autochanger "unload slot
1, drive 1" command.
09-Sep 21:53 bacula-sd JobId 16: 3301 Issuing autochanger "loaded?
drive 1" command.
09-Sep 21:53 bacula-sd JobId 16: 3302 Autochanger "loaded? drive 1",
result: nothing loaded.
09-Sep 21:53 bacula-sd JobId 16: 3304 Issuing autochanger "load slot
1, drive 1" command.
09-Sep 21:53 bacula-sd JobId 16: 3305 Autochanger "load slot 1, drive
1", status is OK.
09-Sep 21:53 bacula-sd JobId 16: Warning: Director wanted Volume "Vol00002".
    Current Volume "Vol00001" not acceptable because:
    1998 Volume "Vol00001" status is Error, but should be Append,
Purged or Recycle.

Then, when I tried to mount manually:

09-Sep 22:38 bacula-sd JobId 16: 3307 Issuing autochanger "unload slot
2, drive 1" command.

# Here, it just unloaded it....... why?, I just loaded it.  Another
thing, I'm looking at this in the logs, why aren't my manual
commands/result messages logged here?

09-Sep 22:39 bacula-sd JobId 16: 3304 Issuing autochanger "load slot
1, drive 1" command.

# And... because of the slot mixum, it tried to load 1 again.... it is
like if it expected to get Vol00002 from slot 1, and it didn't matter
that I had manually loaded it.

09-Sep 22:39 bacula-sd JobId 16: 3305 Autochanger "load slot 1, drive
1", status is OK.
09-Sep 22:39 bacula-sd JobId 16: Warning: Director wanted Volume "Vol00002".
    Current Volume "Vol00001" not acceptable because:
    1998 Volume "Vol00001" status is Error, but should be Append,
Purged or Recycle.
09-Sep 22:39 bacula-sd JobId 16: Please mount Volume "Vol00002" or
label a new one for:
    Job:          servernt-compartidos.2008-09-09_21.30.08
    Storage:      "ULT3-1" (/dev/nst1)
    Pool:         General
    Media type:   ULT-DLT-3

# Second try, same result:

09-Sep 22:48 bacula-sd JobId 16: 3307 Issuing autochanger "unload slot
2, drive 1" command.
09-Sep 22:49 bacula-sd JobId 16: 3304 Issuing autochanger "load slot
1, drive 1" command.
09-Sep 22:49 bacula-sd JobId 16: 3305 Autochanger "load slot 1, drive
1", status is OK.
09-Sep 22:50 bacula-sd JobId 16: Warning: Director wanted Volume "Vol00002".
    Current Volume "Vol00001" not acceptable because:
    1998 Volume "Vol00001" status is Error, but should be Append,
Purged or Recycle.
09-Sep 22:50 bacula-sd JobId 16: Please mount Volume "Vol00002" or
label a new one for:


I hope this helps,

Ildefonso Camargo


On Sat, Sep 13, 2008 at 7:08 AM, Jeronimo Zucco <jczucco AT ucs DOT br> wrote:
> Jeronimo Zucco escreveu:
>>     Hi. I'm using bacula 2.4.2, and I have a pool with a set of tapes.
>> If one of tapes gives s error, instead of try to mount next volume,
>> bacula is blocking the autoloader, like this:
>>
>> Device "Drive-2" (/dev/nst1) is not open.
>>     Device is BLOCKED waiting for mount of volume "QVD021L2",
>>        Pool:        Diary
>>        Media type:  LTO
>>     Drive 0 status unknown.
>>
>>
>>     And I have to manually mount the next tape. This issue is making my
>> backups late. I was using bacula 2.2.8 without any problem until I've
>> upgraded to 2.4.2.
>>
>
>    Yesterday I give up and I've downgraded to bacula 2.2.8, and now
> everithing is working fine again.
>
>    I've tryed to open a bug ticket, but unfortunately I couldn't give
> more information to help bacula developers to solve this issue, sorry.
>
>
>
> --
> Jeronimo Zucco
> LPIC-1 Linux Professional Institute Certified
> Universidade de Caxias do Sul - NPDU
>
> http://jczucco.blogspot.com
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>