Hi Patti,
> Use /dev/sch0, not /dev/sg2. Bear in mind, udev is not your friend. If you
> ever add another tape drive to your library or expand your device fabric,
> these device references will/can change with every system boot. As is, the
> /dev/sgX references can change with reboots, but
-
From: William Muriithi
Sent: Monday, November 5, 2018 11:01 AM
To: Bacula Users Mailing List
Subject: [Bacula-users] Assistance with Autochanger configuration
◆ This message was sent from a non-UWYO address. Please exercise caution when
clicking links or opening attachments from external source
Sorry about the /dev/sch0. I've written udev rules to use consistent names
regardless of what udev does - I do use the /dev/sgX for changer
identification. If you've rebooted your system, the output from lsscsi -g may
have changed. You still need the Drive Index line in your bacula-sd.conf .
On Mon, Nov 5, 2018 at 5:22 PM William Muriithi wrote:
>
> Hello,
>
> We have a quantum superloader 3 that seem to be fine when tested through mt
> and mtx command.
>
> [root@eng-backup02 ~]# lsscsi -g
> [0:2:0:0]diskDELL PERC H710P 3.13 /dev/sda /dev/sg0
> [1:0:2:0]tape
Use /dev/sch0, not /dev/sg2. Bear in mind, udev is not your friend. If you
ever add another tape drive to your library or expand your device fabric, these
device references will/can change with every system boot. As is, the /dev/sgX
references can change with reboots, but if you only have
Hello,
We have a quantum superloader 3 that seem to be fine when tested through mt and
mtx command.
[root@eng-backup02 ~]# lsscsi -g
[0:2:0:0]diskDELL PERC H710P 3.13 /dev/sda /dev/sg0
[1:0:2:0]tapeIBM ULTRIUM-HH6 E4J1 /dev/st0 /dev/sg1
[1:0:2:1]
