-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maria McKinley wrote:
> On 6/14/07, tomasz <[EMAIL PROTECTED]> wrote:
>> Maria McKinley wrote:
>>> tomasz wrote:
Maria McKinley wrote:
> Broderick Wood wrote:
>> I see in another post you say that MTX is working properly from the
>> co
On 6/14/07, tomasz <[EMAIL PROTECTED]> wrote:
> Maria McKinley wrote:
> > tomasz wrote:
> >> Maria McKinley wrote:
> >>> Broderick Wood wrote:
> I see in another post you say that MTX is working properly from the
> command line. This makes me believe that LUN support is enabled.
>
>
Maria McKinley wrote:
> tomasz wrote:
>> Maria McKinley wrote:
>>> Broderick Wood wrote:
I see in another post you say that MTX is working properly from the
command line. This makes me believe that LUN support is enabled.
You should be getting communication problems with MTX if
tomasz wrote:
> Maria McKinley wrote:
>> Broderick Wood wrote:
>>> I see in another post you say that MTX is working properly from the command
>>> line. This makes me believe that LUN support is enabled.
>>>
>>> You should be getting communication problems with MTX if it wasn't. :-)
>>>
>>> BTW
Maria McKinley wrote:
>
> Broderick Wood wrote:
>> I see in another post you say that MTX is working properly from the command
>> line. This makes me believe that LUN support is enabled.
>>
>> You should be getting communication problems with MTX if it wasn't. :-)
>>
>> BTW What Operating Syst
Broderick Wood wrote:
> I see in another post you say that MTX is working properly from the command
> line. This makes me believe that LUN support is enabled.
>
> You should be getting communication problems with MTX if it wasn't. :-)
>
> BTW What Operating System and version are you runnin
Maria McKinley wrote:
> Arno Lehmann wrote:
>> Hi,
>>
>> On 6/13/2007 8:58 PM, Maria McKinley wrote:
>>> Ralf Gross wrote:
Maria McKinley schrieb:
> Falk Sauer wrote:
>> please make shure that your changer device has the correct permissions
>> eg.:
>>
>> crw-rw root d
I see in another post you say that MTX is working properly from the command
line. This makes me believe that LUN support is enabled.
You should be getting communication problems with MTX if it wasn't. :-)
BTW What Operating System and version are you running?
On Wed, 13 Jun 2007 14:48:05 -
Broderick Wood wrote:
> I would also do a quick check to make sure you have LUN support enabled.
>
>
What is LUN support, and how do I check to make sure it is enabled?
~maria
>
> On Wed, 13 Jun 2007 14:24:09 -0700
> Michael Nelson <[EMAIL PROTECTED]> wrote:
>
>> Are you sure that /dev/sg0
I would also do a quick check to make sure you have LUN support enabled.
On Wed, 13 Jun 2007 14:24:09 -0700
Michael Nelson <[EMAIL PROTECTED]> wrote:
> Are you sure that /dev/sg0 is in fact the autochanger device and not the
> tape drive?
>
> For instance on my server (from dmesg output):
>
Arno Lehmann wrote:
> Hi,
>
> On 6/13/2007 8:58 PM, Maria McKinley wrote:
>> Ralf Gross wrote:
>>> Maria McKinley schrieb:
Falk Sauer wrote:
> please make shure that your changer device has the correct permissions
> eg.:
>
> crw-rw root disk /dev/sg0
>
> and for
Are you sure that /dev/sg0 is in fact the autochanger device and not the
tape drive?
For instance on my server (from dmesg output):
(scsi3:A:4): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: CERTANCE Model: ULTRIUM 3 Rev: 1856
Type: Sequential-Access
Hi,
On 6/13/2007 8:58 PM, Maria McKinley wrote:
> Ralf Gross wrote:
>> Maria McKinley schrieb:
>>> Falk Sauer wrote:
please make shure that your changer device has the correct permissions eg.:
crw-rw root disk /dev/sg0
and for the potentially next problem ...
by
Ralf Gross wrote:
> Maria McKinley schrieb:
>> Falk Sauer wrote:
>>> please make shure that your changer device has the correct permissions eg.:
>>>
>>> crw-rw root disk /dev/sg0
>>>
>>> and for the potentially next problem ...
>>> by your tapedrive device i'm unshure, i think this should /dev
An autochanger node should be /dev/sgX
tomasz a écrit :
> Maria McKinley wrote:
>
>> Falk Sauer wrote:
>>
>>> Hi Maria,
>>>
>>>
>>> please make shure that your changer device has the correct permissions eg.:
>>>
>>> crw-rw root disk /dev/sg0
>>>
>>> and for the potentially next
Maria McKinley wrote:
> Falk Sauer wrote:
>> Hi Maria,
>>
>
>> please make shure that your changer device has the correct permissions eg.:
>>
>> crw-rw root disk /dev/sg0
>>
>> and for the potentially next problem ...
>> by your tapedrive device i'm unshure, i think this should /dev/nst0, i d
Maria McKinley schrieb:
> Falk Sauer wrote:
> > please make shure that your changer device has the correct permissions eg.:
> >
> > crw-rw root disk /dev/sg0
> >
> > and for the potentially next problem ...
> > by your tapedrive device i'm unshure, i think this should /dev/nst0, i
> > don't
Falk Sauer wrote:
> Hi Maria,
>
>
> please make shure that your changer device has the correct permissions eg.:
>
> crw-rw root disk /dev/sg0
>
> and for the potentially next problem ...
> by your tapedrive device i'm unshure, i think this should /dev/nst0, i don't
> know how its correct
Hi Maria,
On Wednesday 13 June 2007 writes Maria McKinley:
> I recently updated to version 1.38.11-8, and I am having a hard time
> getting my autochanger to work. I changed my bacula-sd.conf file so that
> there is now an Autochanger:
>
> Autochanger {
>Name = Exabyte
>Device = Drive-1
>
I recently updated to version 1.38.11-8, and I am having a hard time
getting my autochanger to work. I changed my bacula-sd.conf file so that
there is now an Autochanger:
Autochanger {
Name = Exabyte
Device = Drive-1
Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d"
20 matches
Mail list logo
