From: Robert O. <rob...@gm...> - 2014-10-22 08:25:11
Attachments:
smime.p7s
|
Using Bacula Server 7.0.4 on CentOS6_64. One thing which annoys me is that the sg device node for TapeAlert changes with every reboot from /dev/sg4 to /dev/sg6 and vice versa. Is there any setting I can set in udev to get sticky device nodes for my tape device changer device node? System has a LSI 3Ware 9650SE controller installed which is the one fighting for sg device node with my HP Ultrium 4 SCA tape device. Thanks, Robert |
From: Simone C. <neg...@gm...> - 2014-10-22 08:43:50
|
Hello, On 22 October 2014 10:24, Robert Oschwald <rob...@gm...> wrote: > One thing which annoys me is that the sg device node for TapeAlert changes > with every reboot from /dev/sg4 to /dev/sg6 and vice versa. > Is there any setting I can set in udev to get sticky device nodes for my > tape device changer device node? > > System has a LSI 3Ware 9650SE controller installed which is the one > fighting for sg device node with my HP Ultrium 4 SCA tape device. > You use any info from the scsi device and use it to write a rule that matches some of the information. Some examples: http://www.oracle-base.com/articles/linux/udev-scsi-rules-configuration-in-oracle-linux-5-and-6.php http://jhansonxi.blogspot.ch/2009/08/writing-udev-rules-to-get-scsi-scanner.html Regards, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.org/ |
From: Giuseppe V. <giu...@vi...> - 2014-10-22 08:53:09
|
On Wednesday 22 October 2014 10:24:53 Robert Oschwald wrote: > Using Bacula Server 7.0.4 on CentOS6_64. > > One thing which annoys me is that the sg device node for TapeAlert changes with every reboot from /dev/sg4 to /dev/sg6 and vice versa. > Is there any setting I can set in udev to get sticky device nodes for my tape device changer device node? > > System has a LSI 3Ware 9650SE controller installed which is the one fighting for sg device node with my HP Ultrium 4 SCA tape device. > > Thanks, > Robert > > > This is my autochg.sh script under gentoo stable #!/bin/sh sgdev=$(sg_map26 $1) if [ -z "${sgdev}" ]; then echo "TapeAlert: no sgdev for $1" exit 0 fi The command "sg_map26" come from the sg3_utils package that should be available under CentOS6 and make a good job for me converting the tape device into the sg device. Then, in the bacula-sd.conf stanza of your tape or changer, you may use something like this Alert Command = "sh -c '/etc/bacula/autochg.sh /dev/nlto0 | grep TapeAlert|cat'" Seems to work correctly for me. Hope it helps, G. Vitillaro |
From: Clark, P. A. <cl...@or...> - 2014-10-22 12:39:13
|
Cut -n- paste from my 9/22/14 post: lsscsi shows what you currently have. scsi_id -whitelisted -device=/dev/st0 <-- repeat for each tape device and your autochanger device (use /dev/sg#) - this gets you the unique scsi id to be used in the udev rules In your udev rules make sure that you use the nst* reference for tape, it is the no-rewind device. Generally the rules file goes in /etc/udev/rules.d (may be different for your distro). Name it something meaningful to you. Use unique names, not generic ones like "Drive1". Here are a couple of examples for entries - substitute your scsi id output where RESULT==, I like to use * as a catchall for the scsi id: KERNEL=="sg*", SUBSYSTEM=="scsi_generic", PROGRAM="/sbin/scsi_id --whitelisted --replace-whitespace /dev/$name", RESULT=="3221f0090a5004532", ATTRS{type}=="8", SYMLINK+="mychanger" <-- your unique changer name KERNEL=="nst*[0-9]", SUBSYSTEM=="scsi_tape", PROGRAM="/sbin/scsi_id --whitelisted --replace-whitespace /dev/$name", RESULT=="*321110090a5004532*", SYMLINK+="mytape-0" <-- your unique tape drive name for your first drive - repeat for remaining drives There are commands to play with when manipulating the rules and testing, however, I recommend rebooting - it's the final verification. Once you use the command line commands (mtx and mt) and find they behave consistently, then get Bacula involved. Patti Clark Linux System Administrator R&D Systems Support Oak Ridge National Laboratory From: Robert Oschwald <rob...@gm...<mailto:rob...@gm...>> Date: Wednesday, October 22, 2014 at 4:24 AM To: "bac...@li...<mailto:bac...@li...>" <bac...@li...<mailto:bac...@li...>> Subject: [Bacula-users] sg device node stickyness Using Bacula Server 7.0.4 on CentOS6_64. One thing which annoys me is that the sg device node for TapeAlert changes with every reboot from /dev/sg4 to /dev/sg6 and vice versa. Is there any setting I can set in udev to get sticky device nodes for my tape device changer device node? System has a LSI 3Ware 9650SE controller installed which is the one fighting for sg device node with my HP Ultrium 4 SCA tape device. Thanks, Robert |
From: Bryn H. <li...@na...> - 2014-10-22 15:06:29
|
On 14-10-22 01:24 AM, Robert Oschwald wrote: > Using Bacula Server 7.0.4 on CentOS6_64. > > One thing which annoys me is that the sg device node for TapeAlert changes with every reboot from /dev/sg4 to /dev/sg6 and vice versa. > Is there any setting I can set in udev to get sticky device nodes for my tape device changer device node? > > System has a LSI 3Ware 9650SE controller installed which is the one fighting for sg device node with my HP Ultrium 4 SCA tape device. > > Thanks, > Robert > I use the entries in /dev/tape/by-id/ on my servers - not sure if Centos has that implemented or not but it's the best way to ensure a consistent path to a device, even if it changes SCSI controllers or whatever: $ ls -l /dev/tape/by-id/ total 0 lrwxrwxrwx 1 root root 9 Oct 17 07:30 scsi-1IBM_33622LX_002LX23B4384_LL0 -> ../../sg3 lrwxrwxrwx 1 root root 9 Oct 17 07:30 scsi-1IBM_ULT3580-TD3_1210240676 -> ../../st0 lrwxrwxrwx 1 root root 10 Oct 17 07:30 scsi-1IBM_ULT3580-TD3_1210240676-nst -> ../../nst0 Even if you move the tape drive to another machine, your config stays the same - my changer will always be on /dev/tape/by-id/scsi-1IBM_33622LX_002LX23B4384_LL0 and the drive itself will always be at /dev/tape/by-id/scsi-1IBM_ULT3580-TD3_1210240676 Now, if you happen to replace a tape drive or something you will need to update the config, but no matter what else happens on the server the /dev/tape/by-id (and /dev/disk/by-id entries for that matter) will stay the same. Bryn |