Solved

Why doesn't IBMtape appear in the device path for all of my LTO-4 tape devices?

Posted on 2009-05-14
1
992 Views
Last Modified: 2013-12-16
I am having an issue when generating the device tree in Solaris 10. When the path is created with a small number of drives (in this case 2) IBMtape@... appears in the device path like this:
lrwxrwxrwx 1 root root 78 May 13 20:06 0st -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1:st

However, when the device tree is created with 60 drives attached st@... shows up in the device path for 58 out of 60 LTO-4 tape drives.

In the two drive scenario, the media changer and one drive are on VTL port 0a while the second drive is on VLT port 0b. When I create the device paths IBMtape@ &.. shows up in the path.

When I perform the same steps with 30 drives assigned to each port st@ &.. is in the device path. At first glance you would think that the st driver has taken over those devices. Yet a long listing shows the major number is 305. The number 305 is assigned to the IBMtape driver in /etc/name_to_major. I just dont understand the inconsistency in the device path. Does it really matter as long as the driver is IBMtape (305)?

Here is what I currently see:

[root@v240 /]# grep IBMtape /etc/name_to_major

IBMtape 305

[root@v240 /]# ls -l /dev/rmt/*|grep st|wc -l

480 <-- this number equates to the 8 entries created for each of the 60 LTO-4 tape drives.

Here is an example path:

lrwxrwxrwx 1 root root 73 May 14 02:32 /dev/rmt/0st -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/st@w510a09820001922c,1:st

NOTICE the major number is 305 (see below)

# ls -l /devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/st@w510a098

crw------- 1 root sys 305, 1937 May 14 02:38 /devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/st@w510a09820001922c,1:st

All of the device paths look like this with the st@ except for two drives  29st & 59st:

[root@v240 /]# ls -l /dev/rmt/* |grep IBM

lrwxrwxrwx 1 root root 79 May 14 02:32 /dev/rmt/29st -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:st

lrwxrwxrwx 1 root root 80 May 14 02:32 /dev/rmt/29stb -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stb

lrwxrwxrwx 1 root root 81 May 14 02:32 /dev/rmt/29stbn -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stbn

lrwxrwxrwx 1 root root 80 May 14 02:32 /dev/rmt/29stc -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stc

lrwxrwxrwx 1 root root 81 May 14 02:32 /dev/rmt/29stcb -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stcb

lrwxrwxrwx 1 root root 82 May 14 02:32 /dev/rmt/29stcbn -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stcbn

lrwxrwxrwx 1 root root 81 May 14 02:32 /dev/rmt/29stcn -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stcn

lrwxrwxrwx 1 root root 80 May 14 02:32 /dev/rmt/29stn -> ../../devices/pci@1e,600000/SUNW,qlc@3,1/fp@0,0/IBMtape@w510a09820001922c,1e:stn

lrwxrwxrwx 1 root root 77 May 14 02:32 /dev/rmt/59st -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:st

lrwxrwxrwx 1 root root 78 May 14 02:32 /dev/rmt/59stb -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stb

lrwxrwxrwx 1 root root 79 May 14 02:32 /dev/rmt/59stbn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stbn

lrwxrwxrwx 1 root root 78 May 14 02:32 /dev/rmt/59stc -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stc

lrwxrwxrwx 1 root root 79 May 14 02:32 /dev/rmt/59stcb -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stcb

lrwxrwxrwx 1 root root 80 May 14 02:32 /dev/rmt/59stcbn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stcbn

lrwxrwxrwx 1 root root 79 May 14 02:32 /dev/rmt/59stcn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stcn

lrwxrwxrwx 1 root root 78 May 14 02:32 /dev/rmt/59stn -> ../../devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stn

NOTICE the major number is 305 (see below):

#ls -l /devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a

crw------- 1 root sys 305, 3332 May 14 03:09 /devices/pci@1e,600000/SUNW,qlc@3/fp@0,0/IBMtape@w510a09800001922c,1d:stn

The st driver in /etc/name_to_major maps to 33.

I think everything is correct, but I dont understand why the device names are inconsistent.
0
Comment
Question by:cireg
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 

Accepted Solution

by:
cireg earned 0 total points
ID: 24388958
I fixed my problem and here's how I did it:

Removed and re-added the IBMtape driver, removed st device links, and ran devfsadm -Cv.

/opt/IBMtape/tmd -s
rem_drv IBMtape
add_drv -m '* 0666 bin bin' IBMtape
/opt/IBMtape/tmd
/bin/rm /dev/rmt/*
devfsadm -Cv
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

VM backups can be lost due to a number of reasons: accidental backup deletion, backup file corruption, disk failure, lost or stolen hardware, malicious attack, or due to some other undesired and unpredicted event. Thus, having more than one copy of …
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question