Bacula-users

Re: [Bacula-users] new bacula installation

2010-08-12 18:22:06
Subject: Re: [Bacula-users] new bacula installation
From: John Drescher <drescherjm AT gmail DOT com>
To: "Jeremiah D. Jester" <jjest AT u.washington DOT edu>
Date: Thu, 12 Aug 2010 18:19:49 -0400
On Thu, Aug 12, 2010 at 6:05 PM, Jeremiah D. Jester
<jjest AT u.washington DOT edu> wrote:
> A reboot helped. This shows the exact model as /dev/sg2. Now I need to 
> identify the tape drives! :)
>
>
> [root@scrappy ~]# tapeinfo -f /dev/sg2
> Product Type: Medium Changer
> Vendor ID: 'DELL    '
> Product ID: 'PV-124T         '
> Revision: '0075'
> Attached Changer: No
> SerialNumber: 'CK0DB40999'
> SCSI ID: 0
> SCSI LUN: 1
> Ready: yes
>
> DataCompEnabled: yes
> DataCompCapable: yes
> DataDeCompEnabled: yes
> CompType: 0x1
> DeCompType: 0x1
> BOP: yes
> Block Position: 0
>
>
> [root@scrappy ~]# mtx -f /dev/sg2 status
>  Storage Changer /dev/sg2:1 Drives, 8 Slots ( 0 Import/Export )
> Data Transfer Element 0:Full (Unknown Storage Element Loaded):VolumeTag = 
> 000019L4
>      Storage Element 1:Full :VolumeTag=000017L4
>      Storage Element 2:Empty
>      Storage Element 3:Full :VolumeTag=000016L4
>      Storage Element 4:Full :VolumeTag=000012L4
>      Storage Element 5:Full :VolumeTag=000011L4
>      Storage Element 6:Full :VolumeTag=000018L4
>      Storage Element 7:Full :VolumeTag=000013L4
>      Storage Element 8:Full :VolumeTag=000014L4
>


BTW one way to avoid worrying about the device node for the
autochanger is to write a udev rule.

Here is what I have for my autochanger at the moment:
dev6 ~ # cat /etc/udev/rules.d/55-bacula.rules
SUBSYSTEMS=="scsi",ATTRS{vendor}=="EXABYTE*",ATTRS{type}=="8",
SYMLINK+="autochanger1"
SUBSYSTEMS=="scsi",ATTRS{vendor}=="EXABYTE*",ATTRS{type}=="8",
SYMLINK+="changer"


So instead of specifying /dev/sg5 in my bacula config I use
/dev/autochanger1 and udev takes care of finding it for me.

I assume replacing EXABYTE* with DELL* will probably work in your case.

if it does not work for you

udevadm info -a -p  $(udevadm info -q path -n /dev/sg2)

and look what is in ATTRS{vendor}

An example of my output for this command is:

dev6 ~ # udevadm info -a -p  $(udevadm info -q path -n /dev/sg5)

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device
'/devices/pci0000:00/0000:00:0b.0/0000:01:03.0/host8/target8:0:3/8:0:3:1/scsi_generic/sg5':
    KERNEL=="sg5"
    SUBSYSTEM=="scsi_generic"
    DRIVER==""

  looking at parent device
'/devices/pci0000:00/0000:00:0b.0/0000:01:03.0/host8/target8:0:3/8:0:3:1':
    KERNELS=="8:0:3:1"
    SUBSYSTEMS=="scsi"
    DRIVERS==""
    ATTRS{device_blocked}=="0"
    ATTRS{type}=="8"
    ATTRS{scsi_level}=="5"
    ATTRS{vendor}=="EXABYTE "
    ATTRS{model}=="MAGNUM 224      "
    ATTRS{rev}=="C112"
    ATTRS{state}=="running"
    ATTRS{timeout}=="0"
    ATTRS{iocounterbits}=="32"
    ATTRS{iorequest_cnt}=="0x5f"
    ATTRS{iodone_cnt}=="0x5f"
    ATTRS{ioerr_cnt}=="0xd"
    ATTRS{modalias}=="scsi:t-0x08"
    ATTRS{evt_media_change}=="0"
    ATTRS{queue_depth}=="2"
    ATTRS{queue_type}=="none"

  looking at parent device
'/devices/pci0000:00/0000:00:0b.0/0000:01:03.0/host8/target8:0:3':
    KERNELS=="target8:0:3"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device
'/devices/pci0000:00/0000:00:0b.0/0000:01:03.0/host8':
    KERNELS=="host8"
    SUBSYSTEMS=="scsi"
    DRIVERS==""

  looking at parent device '/devices/pci0000:00/0000:00:0b.0/0000:01:03.0':
    KERNELS=="0000:01:03.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="sym53c8xx"
    ATTRS{vendor}=="0x1000"
    ATTRS{device}=="0x0020"
    ATTRS{subsystem_vendor}=="0x1000"
    ATTRS{subsystem_device}=="0x1030"
    ATTRS{class}=="0x010000"
    ATTRS{irq}=="28"
    ATTRS{local_cpus}=="1"
    ATTRS{local_cpulist}=="0"
    ATTRS{modalias}=="pci:v00001000d00000020sv00001000sd00001030bc01sc00i00"
    ATTRS{numa_node}=="0"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}==""
    ATTRS{config}==""

  looking at parent device '/devices/pci0000:00/0000:00:0b.0':
    KERNELS=="0000:00:0b.0"
    SUBSYSTEMS=="pci"
    DRIVERS==""
    ATTRS{vendor}=="0x1022"
    ATTRS{device}=="0x7450"
    ATTRS{subsystem_vendor}=="0x0000"
    ATTRS{subsystem_device}=="0x0000"
    ATTRS{class}=="0x060400"
    ATTRS{irq}=="0"
    ATTRS{local_cpus}=="1"
    ATTRS{local_cpulist}=="0"
    ATTRS{modalias}=="pci:v00001022d00007450sv00000000sd00000000bc06sc04i00"
    ATTRS{numa_node}=="0"
    ATTRS{enable}=="1"
    ATTRS{broken_parity_status}=="0"
    ATTRS{msi_bus}=="1"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

dev6 ~ #

John

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users