HP StorageWorks 7100 - Virtual Array Bedienungsanleitung

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 1

Contents

1 Introduction.......................................................................................................................................2

1.1 About Linux..............................................................................................................................2

1.1.1 General Public License .....................................................................................................2

1.1.2 Linux Support ...................................................................................................................3

1.1.3 How to Get Red Hat Linux ...............................................................................................3

1.2 Hardware Requirements............................................................................................................3

1.3 Operating System Requirements...............................................................................................3

2 Patches ..............................................................................................................................................5

2.1 Command View Patch ..............................................................................................................6

2.1.1 Vendor-Unique Commands ..............................................................................................6

2.1.2 16-Byte SCSI CDBs..........................................................................................................7

2.2 Device “Not Ready – LUN Becoming Ready”.........................................................................9

2.3 Refined SCSI Error Recovery...................................................................................................9

3 Install Patches and Rebuild Kernel.................................................................................................11

4 Install the gimp fonts.......................................................................................................................14

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 2

1 Introduction

The HP Virtual Arrays 7100 and 7400 can be connected to, and managed from, a Linux host. As

tested, the configuration is a direct-connect from the host to the array. One or two controllers may be

used. The Command View SDM software can be installed on Red Hat Linux 6.2, however some

modifications must be made to the Linux host kernel prior to installing the software.

The distinction must be made between supported configurations for host read/writes and for in-band

device management. In configurations that are supported only for host I/O, a separate management

station can be used to monitor and manage the array. Connectivity from the management station to the

array may be through one of the ports of the array or through a hub or switch accessible to the array.

If the array will be configured and managed from another host, e.g., an HPUX system, it is possible to

connect the array directly to a Linux system without making all of the kernel changes described. One

can also configure the HP Virtual Array 7100/7400 via the RS-232 port on the array controllers using

the Virtual Front Panel (VFP). The VFP can be used to establish the correct host port behavior and to

create and delete LUNs, but does not provide array status monitoring, log collection and retention, and

other features.

This document describes the supported Linux configuration for in-band device management.

The HP VA 7100/7400 and Command View SDM software have been tested using QLogic QLA2100

or QLA2200 fibre channel host bus adapters on Red Hat 6.2 with the 2.2.16-3 and 2.2.19-6.2.7 kernels

patched as described herein. Other configurations may work, but are not yet supported. Specifically,

these patches have not been tested in configurations with multiple SCSI devices (i.e., tape drives, CD

ROMs, etc.). The changes to support 16 byte SCSI CDBs may adversely affect the behavior of other

drivers; see the patch descriptions.

Review the patch descriptions before deciding upon which are applicable for your situation.

1.1 About Linux

The Linux OS for personal computers is a UNIX-like OS and meets POSIX standards. It uses a kernel

developed and made freely available by Linus Torvalds (for whom it is named). Originally developed

over the global Internet, Linux has become a widely used OS that involves its users in developing and

testing new features.

1.1.1 General Public License

Linux is supplied as a set of executable files which are accompanied by the corresponding source code.

The files and code can be copied under the terms of a GPL or "General Public License." This means

users can install and use it for free. In exchange, under the GPL, users who make changes in the source

code (to extend the usefulness of the OS on their own installations) are required to make their changes

available to the rest of the user community under the same terms (with source code and free of charge).

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 3

1.1.2 Linux Support

Linux installations can be time-consuming and each requires someone skillful in OS programming.

Distributors of Linux (like Red Hat Software of Research Triangle Park, NC) have created

documentation, service, and support facilities for users who want to install Linux. The kernel and

source code are still freely licensed, but the client pays for the convenience of installing the software as

a package from a CD-ROM. Other services are also available for a fee.

1.1.3 How to Get Red Hat Linux

You can learn how to order Red Hat Linux by contacting the following:

Red Hat Software

2600 Meridian Parkway

Durham , NC 27713

Email [email protected]

World Wide Web http://www.redhat.com

Support is available in the United States by dialing (877) 4REDHAT.

Linux may also be available for purchase at local electronic supply and software stores.

More information is available about Linux from http://www.linux.org.

1.2 Hardware Requirements

Refer to the Command View SDM Installation and User Guide.

The HP VA 7100/7400 may be connected to a Linux host using the QLogic QLA2100/QLA2200 host

bus adapters.

1.3 Operating System Requirements

A clean install of the Red Hat 6.2 i386 Architecture Operating System. Support for remote login and

ftp may be useful, but are not required.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 4

2.2.16 kernel

Linux kernel 2.2.16-3 upgrade. See RedHat site (http://www.redhat.com/support/errata/RHSA-2000-

037-05.html) for background, RPMs and instructions. The RPM packages are:

kernel-headers-2.2.16-3.i386.rpm

kernel-source-2.2.16-3.i386.rpm

kernel-2.2.16-3.i386.rpm

kernel-2.2.16-3.i586.rpm

kernel-2.2.16-3.i686.rpm

kernel-pcmcia-cs-2.2.16-3.i386.rpm

kernel-utils-2.2.16-3.i386.rpm

kernel-ibcs-2.2.16-3.i386.rpm

kernel-doc-2.2.16-3.i386.rpm

kernel-smp-2.2.16-3.i386.rpm

kernel-smp-2.2.16-3.i586.rpm

kernel-smp-2.2.16-3.i686.rpm

kernel-BOOT-2.2.16-3.i386.rpm

2.2.19 kernel

Linux kernel 2.2.19 upgrade. See RedHat site (https://www.redhat.com/support/errata/RHSA-2001-

047.html) for background, RPMs and instructions. The RPM packages and commands to install are:

rpm -Uvh db3-3.1.17-4.6x.i386.rpm

rpm -Uvh rpm-4.0.2-6x.i386.rpm

rpm -Uvh mount-2.10r-0.6.x.i386.rpm

rpm -Uvh nfs-utils-0.3.1-0.6.x.1.i386.rpm

rpm -ivh kernel-BOOT-2.2.19-6.2.7.i386.rpm

rpm -ivh kernel-2.2.19-6.2.7.i386.rpm

rpm -ivh kernel-headers-2.2.19-6.2.7.i386.rpm

rpm -ivh kernel-source-2.2.19-6.2.7.i386.rpm

rpm -ivh kernel-ibcs-2.2.19-6.2.7.i386.rpm

rpm -Uvh kernel-pcmcia-cs-2.2.19-6.2.7.i386.rpm

rpm -ivh kernel-doc-2.2.19-6.2.7.i386.rpm

Kernel upgrade procedure

The procedure for upgrading the kernel is documented at:

http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html

If you are not already familiar with building a Linux kernel, please read the directions for your

architecture carefully before proceeding with the kernel upgrade.

The recommended upgrade path is to install the Linux kernel headers and source, build the kernel for

your machine to confirm that all components needed to build are in place, then apply the patches and

build the new version (e.g., 2.2.19-6.2.7HP). This is a bit safer; by retaining the ability to boot into the

original kernel you are not left at the mercy of your backup boot disk in case something goes wrong.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 5

# rpm -Uvh kernel-headers-2.2.19-6.2.7.i386.rpm

# rpm -Uvh kernel-source-2.2.19-6.2.7.i386.rpm

Build the base kernel.

2 Patches

After the kernel has been upgraded, consider applying the following patches to the Kernel’s SCSI

subsystem source code.

The patches are listed here and summarized below.

1. Command View

2. Device “Not Ready – LUN Becoming Ready”

3. Refined SCSI Error Recovery

There are versions of these patches for the Linux 2.2.16-3 and 2.2.19 kernels. The changes can be

reached from http://www.hp.com. Follow the links to the VA 7100/7400 mid-range disk array storage

products.

The patches are commented so that they are easily discernable from the baseline code and so that you

can distinguish between the changes applicable for each patch.

Each change section is bracketed with “begin” and “end” patch tag comments. The comments are of

the form:

<patch tag> <description> <date> {begin | end}

The patch tag, HP_VA7100, indicates the Hewlett-Packard patch for the Virtual Array 7x00. The

description summarizes its purpose, and the date indicates the timeliness of the patch; newer versions

of the patch will have more recent dates. The “begin” will appear as the first line of a section of code

that has been modified, and the “end” will appear after each modified change section.

This set of patches is commented as follows:

HP_VA7100 vendor unique data direction 2001-03-15

HP_VA7100 16 byte CDB 2001-03-15

HP_VA7100 device not ready - LUN becoming ready 2001-03-15

HP_VA7100 refined error recovery 2001-03-15

Packaging

The patches can be found in the following patch files (packaged for the applicable kernel):

Command_View_2.2.16.patch

Command_View_2.2.19.patch - contains the patches needed to run HP Command View SDM

software on a Linux host. This includes the “vendor unique data direction” and “16 byte CDB”

patches.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 6

Device_Not_Ready_2.2.16.patch

Device_Not_Ready_2.2.19.patch - contains the “device not ready – LUN becoming ready” patch.

Error_Recovery_2.2.16.patch

Error_Recovery_2.2.19.patch - contains the “refined error recovery” patch.

These patches can be applied separately depending upon your requirements. In addition to these pre-

packaged patches, there is another minor change that should be made prior to re-building the kernel.

See the steps under “Install Patches and Rebuild Kernel” below.

Before applying any of these patches, be sure to read the descriptions below. There are tradeoffs to be

made with the implementation of these patches; you should be aware of the potential impacts of each.

2.1 Command View Patch

The Command View patch includes two distinguishable changes. One to set the data direction for

vendor-unique commands, and another to allow SCSI Command Data Blocks sized up to 16 bytes to

be passed through the kernel. These are described below.

2.1.1 Vendor-Unique Commands

Problem synopsis: The Linux 2.2 kernel SCSI generic (sg) API does not contain an explicit data

direction field for SCSI commands. The SCSI low-level drivers, qlogicfc in particular, must “snoop”

the SCSI opcode within the CDB to determine data direction from a standard lookup table. This

procedure does not work with vendor unique commands because data direction is product specific.

The specific operation codes for which the patch is applied are:

0x27

0x29

0xe2

0xed

0xf9

0xfa

0xfd

Patch description: The most straightforward solution is to patch the qlogicfc driver code where

SCSI opcodes are being snooped. Since the default data-direction is assumed to be data-in, we

explicitly add the vendor/product-unique commands that have a data-out phase. We also add a few

missing SCSI-3 commands to the qlogicfc driver (FORMAT_UNIT, SEND_DIAGNOSTIC,

WRITE_LONG, WRITE_SAME, MODE_SELECT_10, WRITE_12, WRITE_VERIFY_12, and

SEND_VOLUME_TAG). Each of these commands also has a data-out phase.

Caveats: Because a certain range of opcodes is reserved for vendor-unique (product specific)

SCSI commands, it is possible that one product may define a certain opcode to have a data-in phase

while another product from a different vendor may define the same opcode to require a data-out phase.

In this case, simply “snooping” the opcode would not be sufficient.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 7

Recommendation: This patch is required if managing the VA 7100/7400 through a Linux host. If

other device management options are pursued, this patch is not required.

Files Affected: ../linux/drivers/scsi/qlogicfc.c

2.1.2 16-Byte SCSI CDBs

Problem synopsis: The Linux 2.2 kernel SCSI subsystem supports command descriptor blocks

(CDBs) up to 12 bytes in length. The constant, MAX_COMMAND_SIZE, defines this length but is

not used consistently throughout the SCSI source code. In many places a CDB size of 12 bytes is

hard-coded. Several management features specific to the VA 7100/7400 require 16-byte CDBs.

Patch description: This patch to the SCSI mid-layer removes all hard-coded size restrictions on

CDB data structures. All such data structures now reference the MAX_COMMAND_SIZE constant,

which has also been increased to 16 bytes.

Caveats: This patch applies to the entire SCSI subsystem, not just fibre-channel devices. All

processing of SCSI command data structures will now involve manipulating a 16-byte field instead of

the typical 12 bytes. This is a modest amount of overhead to support the few commands which require

16-byte CDBs.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 8

This patch has been tested successfully with Qlogic fibre-channel host adapters using the qlogicfc and

Qlogic qla2x00 drivers. The impact of this patch on other SCSI drivers (especially legacy drivers) has

not been fully assessed. It is not exhaustively known, for example, how a legacy host adapter will

behave if its respective driver makes assumptions about CDB length and passes the full 16 bytes of

data down to hardware which is limited to receive only 12-bytes. This change will adversely affect the

following drivers; there may be others in addition to these:

53c7xx (only 12 bytes copied)

53c7,8xx (corrupts structures)

sym53c8xx

Buslogic Flashpoint (Firmware can’t do 16 byte commands)

NCR 53c9x (16 byte commands not supported)

AHA1542 (only 12 byte commands handled by hardware)

cpqfcTSinit (assumption in driver about kernel only)

eata (command corrupts structures in device)

esp (driver assumes no 16 byte commands exist)

i91uscsi (driver assumes 12 byte buffers internally)

ide-scsi (kernel buffer of 12 bytes, causes stack corruption)

in2000 (driver assumes 12 bytes internal)

ini9100u (driver assumes 12 byte structs)

ips (driver assumes 12 byte structs)

qlogicpti

sim710 (driver assumption)

tmscsim

u14-34f (corrupts driver structs)

ultrastor (corrupts driver structs)

wd33c93

wd7000 (corrupts driver structs)

Recommendation: This patch is required if managing the VA 7100/7400 through a Linux host. If

other device management options are pursued, this patch is not required.

Files Affected: ../linux/drivers/scsi/scsi.c

../linux/drivers/scsi/scsi.h

../linux/drivers/scsi/scsi_ioctl.c

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 9

2.2 Device “Not Ready – LUN Becoming Ready”

Problem synopsis: The Linux 2.2 kernel SCSI subsystem does not appear to distinguish the various

kinds of “Not Ready” device states. Some “Not Ready” sense codes indicate that a device is not ready

and will require manual intervention in order to become ready (such as the case when media has been

removed from a tape device). However, other “Not Ready” codes indicate that the device is not yet

ready, but is in the process of becoming ready (such as during device initialization or self-diagnostic).

In the latter case, the LUN is said to be “becoming ready” and all that is required is a retry. The VA

7100/7400 can be in this “becoming ready” state for periods of up to 15 seconds, or more, during

initialization, which typically causes the Linux subsystem to take the device offline, resulting in data

loss and/or filesystem corruption.

Patch description: When the device reports a state of “Not Ready - LUN becoming ready”, this

patch will re-queue the command at the high-level sd driver. In this case we know the device will soon

be available and it is preferable to wait rather than to give up.

Caveats: While the device is in this particular “becoming ready” state, there is currently no delay

between command retry attempts.

Recommendation: Use this patch at your discretion. If the array needs to be re-initialized and you

notice lengthy “becoming ready” periods, this patch should be considered.

Files Affected: ../linux/drivers/scsi/sd.c

2.3 Refined SCSI Error Recovery

Problem synopsis: The Linux 2.2 kernel SCSI subsystem provides a reference (sample) error

recovery function called scsi_unjam_host. This routine does not have ideal behavior for time-

outs and it tends to mark fibre-channel devices offline with very little provocation. This action usually

results in data loss and/or filesystem corruption, as well as irremovable locked system processes. In

the event of a time out that exceeds the 30-second default value, the error recovery thread is awakened

and, after some attempts to reset the missing device, it is marked offline resulting in filesystem

corruption and hung processes.

Patch description: Fortunately, the Linux 2.2.16 (and .19) SCSI subsystem provides a “new” error

handling architecture whereby the default error recovery function can be overridden within each low-

level driver. This patch to the qlogicfc driver implements the new SCSI error handling mechanism and

supplies an alternate error recovery behavior which affects only devices attached to the Qlogic adapter.

Other SCSI devices on the system continue to use the scsi_unjam_host function and retain their

normal recovery behavior. The scsi_unjam_host routine was copied from scsi_error.c to

qlogicfc.c and modified as an example of how to customize error recovery for a particular

environment. On inserting the modified qlogicfc module into the kernel, the driver registers its error

handling function, now called isp2x00_strategy_handler, with the SCSI host’s

eh_strategy_handler function pointer. The isp2x00_strategy_handler function is

now called in place of scsi_unjam_host for Qlogic-attached devices.

Linux Configuration

HP VA 7100/7400

Rev 2002-01-23 Page 10

The major distinguishing behavior of the new recovery function is that there are now very few

conditions in which a device will ever be marked offline.

More specifically, the new error handler function will attempt to abort and retry any outstanding

commands that have failed or timed out. If this retry also fails, the function will wait 15 seconds and

try again. It continues aborting/retrying every 15 seconds for up to 5 minutes. At 5 minutes, it

attempts to reset the offending device (this reset function does not appear to be implemented in the

qlogicfc driver), if this reset fails, it attempts to reset the bus, and then finally the host adapter itself. If

none of these resets allows for successful retirement of outstanding SCSI commands, the new error

recovery function loops back and begins the entire recovery process from the top. This continues

indefinitely until the device returns. The code is very straightforward and can be easily customized to

eventually mark the device offline if desired, after any combination or duration of aborts/retrys/resets.

It should be noted that the qla2x00.c driver, which is available from Qlogic’s web page, attempts to

address this same issue with what they refer to in their code as a “SCSI kluge”. Their solution involves

detecting when the fibre-channel loop is down and bumping the timer values on outstanding SCSI

commands to prevent them from timing out. They then perform their own retries from a separate low-

level command queue. The qla2x00.c driver does not currently take advantage of the new error

handling architecture and does not address the case where a device is timing out but is still present on

the fibre-channel loop. In such cases, a timeout that occurs against a device that is still present on the

loop can still result in that device being marked offline with data loss and/or filesystem corruption.

The “SCSI kluge” provided with that driver protects only against timeouts that occur because the link

is down (device unplugged from the loop).

Caveats: The behavior of our patch to the qlogicfc.c driver is not yet ideal. It assumes that a

missing or timed-out device will eventually return to its original position. If the device will not return,

or returns in some other device location on the system, then there is currently no means in place to

manually notify the new error handler that it should give up and mark the missing device offline.

While the error recovery function is activated, all new or existing processes with outstanding I/O to

that Qlogic HBA will remain blocked in error recovery waiting for the device to return, and they

cannot be killed. We have made the assumption that “missing devices that never return” will be rare

and that our approach is preferable to the potential for lost data or filesystem corruption for “missing

devices that eventually return”. In any case, this patch is offered as a safeguard and an example which

can be easily customized to provide a wide range of recovery policies specifically suited to Qlogic-

attached devices.

Andere Handbücher für StorageWorks 7100 - Virtual Array

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Andere HP Lagerung Handbücher

HP P9000 Bedienungsanleitung

HP StorageWorks Disk System 2405 Gebrauchs- und Pflegehandbuch

HP POD 40c G2 Handbuch

HP S650 Bedienungsanleitung

HP StorageWorks 8B - FC Entry Switch Bedienungsanleitung

HP StorageWorks NAS b2000 - v2 Bedienungsanleitung

HP Surestore 6164 - Switch Bedienungsanleitung

HP 3PAR StoreServ 7000 Bedienungsanleitung

HP StorageWorks 4000/6000/8000 - Enterprise Virtual... Bedienungsanleitung

HP 3PAR StoreServ 7000 Bedienungsanleitung

HP P2000 G3 Bedienungsanleitung

HP 705 Kurzanleitung

HP Ultrium Drive Produkthandbuch

HP 201723-B21 - HP StorageWorks Modular SAN Array 1000 Hard... Bedienungsanleitung

HP SCSI Ultra320 Installationsanleitung

HP StorageWorks 4000/6000/8000 - Enterprise Virtual... Bedienungsanleitung

HP 3000 - 37XE System Bedienungsanleitung

HP SureStore DAT40e Bedienungsanleitung

HP StorageWorks P2000 Bedienungsanleitung

HP StorageWorks 2300 - Disk System Kurzanleitung

HP P9000 Bedienungsanleitung

HP StorageWorks P2000 Bedienungsanleitung

HP Converged Architecture 700 Kurzanleitung

HP StorageWorks ESL9000 Series Bedienungsanleitung

Beliebte Lagerung Handbücher anderer Marken

QNAP

QNAP TS 32PXU Series Bedienungsanleitung

LaCie

LaCie RUGGED RAID Bedienungsanleitung

Freecom

Freecom CLS DOCK Bedienungsanleitung

PNY

PNY Attache P-FD64MBATT3 Bedienungsanleitung

OLT

OLT 6x6 Maximizer Bedienungsanleitung

Transcend

Transcend JetFlash 160 Bedienungsanleitung

LaCie

LaCie RUGGED MINI Bedienungsanleitung

Thunderbolt

Thunderbolt 600 Bedienungsanleitung

Panasonic

Panasonic LB-DH8 series Handbuch

Intel

Intel RAID High Availability Bedienungsanleitung

LaCie

LaCie 12big Thunderbolt 3 Bedienungsanleitung

Spectra Logic

Spectra Logic T-Series Spectra T50e Bedienungsanleitung

Panasonic

Panasonic LKM-F931-1 Bedienungsanleitung

Tabernus

Tabernus Enterprise Erase E2400 Bedienungsanleitung

Rocstor

Rocstor COMMANDER 3F series Bedienungsanleitung

Western Digital

Western Digital Ultrastar Data60 Bedienungsanleitung

Dell

Dell PowerVault MD3600f Series Bedienungsanleitung

CFI

CFI TERA STOR SATA RAID IV Bedienungsanleitung