SUMMARY: How do I determine rzXX device name for a new disk

From: Izzet Ergas <izzet.ergas_at_citrix.com>
Date: Mon, 07 Aug 2000 09:20:37 -0400

Thanks to alan_at_nabeth.cxo.dec.com, Charles M. Richmond,
jreed_at_wukon.appliedtheory.com, Ron Bramblett, John J. Francini, Stephen L.
Tycer, Jim Kurtenbach, Raul Sossa S., Alan Davis, Richard Bond and Narendra
Ra[a]vi for responding.

> -----Original Message-----
> From: Izzet Ergas [mailto:izzet.ergas_at_citrix.com]
> Sent: Friday, August 04, 2000 4:57 PM
> To: 'Tru64-UNIX-Managers'
> Subject: How do I determine rzXX device name for a new disk
>
> Config: ES40, Tru64 4.0F and HSZ80 controllers
>
> I'm trying to get the OS to recognize some new storagesets I've created on
HSZ80. Apparently, one of the steps in the procedure is to execute "MAKEDEV
rzXX" where XX is some number derived from the SCSI target ID and LUN # of
the disk to be configured. How do I determine what the value of XX is?



        rz{a-h}# where:

        The first {a-h} is a letter to indicate the SCSI logical
        unit number of the HSZ unit. a = LUN 0, b = LUN 1,
        c = LUN 2, etc. You don't need to use a for the LUN 0
        devices since this is also the base name of rz#.

        The # is found the SCSI bus number that the controller
        is on and the SCSI target ID:

                # = (bus * 8) + target

        V4 and earlier versions doesn't support wide SCSI
        addressing (target IDs 8-15).

        So, if you have a unit named D101 on the HSZ side,
        this would be target ID 1, LUN 1. If it is on the
        host SCSI bus 3, it would be:

                (3 * 8) + 1 = 25 and b for LUN 1

                rzb25

        The device D0 on the same bus would be:

                (3 * 8) + 0 = 24, a or nothing for LUN 0

                rz24

        This is described in the SCSI manual page.

        In general if using multiple logical units per target
        it is better to use up all the available targets before
        using logical units other than zero. The host drive
        allocates the ability to use queued commands by target.
        Using all the LUNs on a given target would restrict that
        target to a small share of queued commands.

        On the other hand, if you use tapes on the HSZ family,
        there isn't an easy to create the special files for
        non-LUN 0 tape drives. Rebooting the system will
        create the files if they don't exist, but a subsystem
        like the HSZ80 allows for very flexible dynamic reconfig-
        uration, and rebooting isn't necessary to change devices
        around.

Use SCU to see what devices exist on your various SCSI buses. Here's
an example from a system with an HSZ70 connected to it:

# /sbin/scu
scu> show edt

CAM Equipment Device Table (EDT) Information:

     Device: RRD45 Bus: 0, Target: 5, Lun: 0, Type: Read-Only Direct
Access
     Device: HSZ70 Bus: 1, Target: 0, Lun: 0, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 0, Lun: 1, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 0, Lun: 2, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 0, Lun: 3, Type: Direct Access
     Device: HSZ70CCL Bus: 1, Target: 0, Lun: 4, Type: Direct Access
* Device: HSZ70 Bus: 1, Target: 1, Lun: 0, Type: Direct Access
* Device: HSZ70 Bus: 1, Target: 1, Lun: 1, Type: Direct Access
* Device: HSZ70 Bus: 1, Target: 1, Lun: 2, Type: Direct Access
* Device: HSZ70 Bus: 1, Target: 1, Lun: 3, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 2, Lun: 0, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 2, Lun: 1, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 2, Lun: 2, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 2, Lun: 3, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 3, Lun: 0, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 3, Lun: 1, Type: Direct Access
     Device: HSZ70 Bus: 1, Target: 3, Lun: 2, Type: Direct Access
     Device: RZ28M Bus: 2, Target: 0, Lun: 0, Type: Direct Access
     Device: RZ28M Bus: 2, Target: 1, Lun: 0, Type: Direct Access
     Device: RZ28M Bus: 2, Target: 2, Lun: 0, Type: Direct Access
     Device: RZ26L Bus: 2, Target: 4, Lun: 0, Type: Direct Access


For example:

Say you added the drives represented by the lines above with an
asterisk in front of them.

The disk on Bus 1 target 2 Lun 0 would be rz10
The disk on Bus 1 target 2 lun 1 would be rzb10;
likewise on bus 1 target 2 lun 2 would be rzc10
and ditto bus 1 target 2 lun 3 would be rzd10.

Bus 1 devices are rz8xxx through rz14xxx
Bus 2 devices are rz16xxx through rz22xxx
Bus 3 devices are rz24xxx through rz30xxx
etc -- adding 8 the values for each additional bus.

so you would then do:

        # cd /dev
        # ./MAKEDEV rz10
        # ./MAKEDEV rzb10
        # ./MAKEDEV rzc10
        # ./MAKEDEV rzd10

(MAKEDEV output not shown for clarity.) If the MAKEDEV works, you'll
get a list of 16 devices for both character and block mode access to
all 8 possible partitions on a physical disk.
Received on Mon Aug 07 2000 - 13:22:16 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT