Hi Pedro,

Thanks for the link.  I actually looked at it before Hartge responded and funny 
enough came to the same conclusion.  The info maps the tape nicely but I don't 
get enough info from udev to do the dame with autochanger.

I only get this:

[root@eng-backup01 etc]# udevadm info --name=/dev/sch0  --query=all
P: 
/devices/pci0000:40/0000:40:02.0/0000:42:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:1/scsi_changer/sch0
N: sch0
E: DEVNAME=/dev/sch0
E: 
DEVPATH=/devices/pci0000:40/0000:40:02.0/0000:42:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:1/scsi_changer/sch0
E: MAJOR=86
E: MINOR=0
E: SUBSYSTEM=scsi_changer

Regards,
William
________________________________________
From: Sven Hartge <s...@svenhartge.de>
Sent: March 3, 2019 10:21 AM
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Persistent device name for autochanger

On 03.03.19 16:00, Pedro Oliveira wrote:

> https://nonhazardo.us/tape/storage/udev/2016/03/14/udev-persistent-tape-drive-naming.html

This is all well and fine, but only talks about /dev/stX and /dev/nstX.
But persitently naming the tape devices is not the question here.

The real question is on how to peristently name the *generic* SCSI
device associated with the tape changer.

The values you get inside udev for scsi_generic are rather sparse:

P:
/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:04.0/host6/target6:0:2/6:0:2:0/scsi_generic/sg5
N: sg5
L: 0
E:
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:02:00.0/0000:03:04.0/host6/target6:0:2/6:0:2:0/scsi_generic/sg5
E: DEVNAME=/dev/sg5
E: MAJOR=21
E: MINOR=5
E: SUBSYSTEM=scsi_generic
E: USEC_INITIALIZED=29531657


Nothing really helpful to base a rule on, IMHO.

Grüße,
Sven.



_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to