Hi Skylar, Yes, all drives are LTO drives (SAN attached). I tried your procedure, but it's not working. The six tape devices are all actually there:
# ls -al /dev/IBMtap* crw------- 1 root root 235, 0 Feb 2 17:04 /dev/IBMtape0 crw------- 1 root root 235, 1024 Feb 2 17:04 /dev/IBMtape0n crw------- 1 root root 235, 1 Feb 2 17:04 /dev/IBMtape1 crw------- 1 root root 235, 1025 Feb 2 17:04 /dev/IBMtape1n crw------- 1 root root 235, 2 Feb 2 17:04 /dev/IBMtape2 crw------- 1 root root 235, 1026 Feb 2 17:04 /dev/IBMtape2n crw------- 1 root root 235, 3 Feb 2 17:04 /dev/IBMtape3 crw------- 1 root root 235, 1027 Feb 2 17:04 /dev/IBMtape3n crw------- 1 root root 235, 4 Feb 2 17:04 /dev/IBMtape4 crw------- 1 root root 235, 1028 Feb 2 17:04 /dev/IBMtape4n crw------- 1 root root 235, 5 Feb 2 17:04 /dev/IBMtape5 crw------- 1 root root 235, 1029 Feb 2 17:04 /dev/IBMtape5n But one persistent named device is just not created: # ls -l /dev/lin_tape/by-id/ total 0 lrwxrwxrwx 1 root root 17 Feb 2 17:04 changer0 -> ../../IBMchanger4 lrwxrwxrwx 1 root root 14 Feb 2 17:04 drive1 -> ../../IBMtape5 lrwxrwxrwx 1 root root 14 Feb 2 17:04 drive2 -> ../../IBMtape2 lrwxrwxrwx 1 root root 14 Feb 2 17:04 drive3 -> ../../IBMtape3 lrwxrwxrwx 1 root root 14 Feb 2 17:04 drive4 -> ../../IBMtape0 lrwxrwxrwx 1 root root 14 Feb 2 17:04 drive5 -> ../../IBMtape4 I'm missing drive6 for some reason. I double-checked the serials in the 98-lin_tape.rules file and compared them to the output of the cat /proc/scsi/IBMtape command and they are all correct... Thanks for your help! Kind regards, Eric van Loon -----Original Message----- From: ADSM: Dist Stor Manager <ADSM-L@VM.MARIST.EDU> On Behalf Of Skylar Thompson Sent: Thursday, 2 February 2023 16:56 To: ADSM-L@VM.MARIST.EDU Subject: Re: Removing tape devices Are these all IBM LTO drives using the lin_tape driver? My experience on RHEL7 w/ FC-attached drives is that the devices show up automatically, though I can't remember if it removes them if the drive falls off the fabric. I suspect not, just so that a transient problem doesn't leave the system in an inconsistent state. You might try unloading the kernel module to get rid of the devices: modprobe -r lin_tape And then ask udev to reprocess its rules and clean up device links it can't find: udevadm trigger That assumes the WWNs of the drives in your udev rules don't need updating. At that point, you ought to be able to re-load lin_tape: modprobe lin_tape If you're having trouble getting the drives to show up afterwards, you might try a FC LIP: echo 1 > /sys/class/fc_host/hostX/issue_lip Followed by a SCSI rescan: echo "- - -" > /sys/class/scsi_host/hostN/scan On Thu, Feb 02, 2023 at 03:38:21PM +0000, Loon, Eric van (ITOP DI) - KLM wrote: > Hi everybody, > > I'm having some issues with missing persistent names after a HBA replacement > on a Linux server. I like to remove all tape devices, so all /dev/IBMTape*, > all /dev/lin_tape/by-id/drive* devices and the SCSI devices. What is the > proper way to do that in Linux? > Afterwards, I like to run a SCSI rescan to have everything redefined, so I > can start with a clean sheet. > Thanks for any help in advance! > > Kind regards, > Eric van Loon > Air France/KLM > ******************************************************** > For information, services and offers, please visit our web site: > https://urldefense.com/v3/__http://www.klm.com__;!!K-Hz7m0Vt54!mj3-YqICmARjV6b_WPIXbqoM-r_YP44rh-TgAQqwCFuCBlztgWcHLVxjPSTXJa99xAcg2QUJQVSJle1GprJKpQ$ > . This e-mail and any attachment may contain confidential and privileged > material intended for the addressee only. If you are not the addressee, you > are notified that no part of the e-mail or any attachment may be disclosed, > copied or distributed, and that any other action related to this e-mail or > attachment is strictly prohibited, and may be unlawful. If you have received > this e-mail by error, please notify the sender immediately by return e-mail, > and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission of > this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > ******************************************************** -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department (UW Medicine), System Administrator -- Foege Building S046, (206)-685-7354 -- Pronouns: He/Him/His ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************
