Re: [Bacula-users] [Bacula-devel] No slots in changer to scan.
2008-09-04 14:45:06
Kern,
The MTX version (1.3.11) I was using that had that problem is the same
one found in depkgs-22Feb08.tar.gz
Here's the explanation the mtx programmer put in the release notes for
the newer version "Release 1.3.12 of the stable version of MTX fixes a
problem when UNIT ATTENTION is pending when mtx is started. This can
occur if the door is opened on some libraries or the SCSI bus is reset.
The change eliminates the requirement to rerun the mtx command."
There may be a separate configuration issue causing "update slots" to
prompt for a drive but other people have acknowledged it too on the
bacula-user's list. Since you said you're not getting it I once again
verified my config based on the documentation online at www.bacula.org
to no avail, it still prompts for a drive, so here's the relevant
sections of my configs...
taken from my bacula-dir.conf
Storage {
Name = Dell-PV136T
Autochanger = yes
Address = gyrus
SDPort = 9103
Device = Dell-PV136T
Media Type = LTO-2
Password = ""
Maximum Concurrent Jobs = 8
}
===
taken from my bacula-sd.conf
Autochanger {
Name = Dell-PV136T
Device = IBMLTO2-1, IBMLTO2-2
Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
Changer Device = /dev/sg3
}
Device {
Name = IBMLTO2-1
Drive Index = 0
Media Type = LTO-2
Archive Device = /dev/nst0
Changer Device = /dev/sg3
AutomaticMount = yes
AlwaysOpen = yes
Label Media=yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = yes
SpoolDirectory = /tmp/raid0cache/baculaspool
Maximum Spool Size = 200gb
Requires Mount = no
Alert Command = "sh -c '/usr/local/sbin/smartctl -H %c'"
}
Device {
Name = IBMLTO2-2
Drive Index = 1
Media Type = LTO-2
Archive Device = /dev/nst1
Changer Device = /dev/sg3
AutomaticMount = yes
Label Media=yes
AlwaysOpen = yes
RemovableMedia = yes
RandomAccess = no
AutoChanger = yes
SpoolDirectory = /tmp/raid0cache/baculaspool
Maximum Spool Size = 200gb
Requires Mount = no
Alert Command = "sh -c '/usr/local/sbin/smartctl -H %c'"
}
Kern Sibbald wrote:
> Hello,
>
> Are you saying that this is a bug in mtx? If so, do you know what versions
> have the problem and in which version it is fixed? Having the version
> information is rather important because I imagine that most people such as
> myself use the version that is installed by the distribution.
>
> Also, I'm wondering if a configuration problem isn't causing problems.
> Normally for doing an update slots, you should be using the Autochanger
> resource -- i.e. the name of the autochanger and not the name of a particular
> drive. The output below seems to be referring to a particular drive such as
> Drive-0 or Drive-1, and I am wondering if that is correct. The silly command
> prompt for "update slots" seems to ask for a drive number (I have two drives,
> and think this prompt really should not be there and is probably ignored),
> but when I do an update slots, it never prints anything about an individual
> drive name, but always refers to the autochanger (mine is called
> LTO-changer).
>
> Best regards,
>
> Kern
>
> On Thursday 04 September 2008 16:29:02 Bob Hetzel wrote:
>> Previously, "Vladislav Korotkov" <v.korotkov AT cti DOT ru> said
>>
>>> Sometimes after I issue `update slots' command I get:
>>>
>>> No slots in changer to scan.
>>>
>>> When I run the command once (twice) again , everything is fine, the
>>> slots' status is updated:
>>>
>>> *update slots
>>>
>>> Automatically selected Catalog: MyCatalog
>>>
>>> Using Catalog "MyCatalog"
>>>
>>> Automatically selected Storage: Autochanger
>>>
>>> Connecting to Storage daemon Autochanger at tmmsk.kosmos.cti.ru:9103 ...
>>>
>>> 3306 Issuing autochanger "slots" command.
>>>
>>> Device "Drive-1" has 0 slots.
>>>
>>> No slots in changer to scan.
>>>
>>> *update slots
>>>
>>> Automatically selected Storage: Autochanger
>>>
>>> Connecting to Storage daemon Autochanger at tmmsk.kosmos.cti.ru:9103 ...
>>>
>>> 3306 Issuing autochanger "slots" command.
>>>
>>> Device "Drive-1" has 23 slots.
>> I got this behavior whenever I opened my tape library. Recently, I
>> reported it to the mtx-general mailing list and there is now a new
>> version available at
>> http://sourceforge.net/project/showfiles.php?group_id=4626.
>>
>> I suggest any of you with a this issue give it a go and report back to
>> the mtx-general mailing list. I've been running the new 1.3.12 version
>> for a couple weeks now without any negative side effects.
>>
>> I'm cc: the bacula developers list in case they're not aware of this
>> newer version yet and would like to test with it as well.
>>
>> Bob
>>
>> -------------------------------------------------------------------------
>> 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-devel mailing list
>> Bacula-devel AT lists.sourceforge DOT net
>> https://lists.sourceforge.net/lists/listinfo/bacula-devel
>
>
-------------------------------------------------------------------------
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
|
|
|