mirror of
https://github.com/systemd/systemd.git
synced 2025-01-14 23:24:38 +03:00
e92a3d8fa3
Some SCSI tape devices use the same device ID (NAA registered device designator) for the SCSI tape changer device and the first actual tape device. For example, this one: https://docs.oracle.com/en/storage/tape-storage/storagetek-sl150-modular-tape-library/slofs/bridged-tape-drives.html You must connect the bridged drive to an HBA supporting multiple LUNs (also referred to as LUN scanning). The SL150 Library uses a single SCSI ID and two logical unit numbers (LUN). LUN 0 controls the tape drive and LUN 1 which is configured as a SCSI medium changer device controls the robotics. Data is sent to the remaining LUN on the bridged drive or to LUNs on the other, unbridged drives in the partition, all of which are configured as SCSI sequential-access (tape) devices. This may lead to errors because /dev/tape/by-id symlinks may sometimes point to the st device representing the tape, and sometimes to the sg device representing the changer. Fix this by assigning an increased priority to the tape device, and creating a separate -changer link for the SCSI tape changer. Co-developed-by: Martin Wilck <mwilck@suse.com>
Files in this directory contain configuration for systemd-udevd.service, a daemon that manages symlinks to device nodes, permissions of devices nodes, emits device events for userspace, and renames network interfaces. See man:udev(7) for an overview of the configuration file format, and man:systemd-udevd.service(8) for a description of service itself. Use 'systemd-analyze cat-config udev/rules.d' to display the effective config.