IBM(R) System Storage Multipath Subsystem Device Driver Version 1.6.3.0-8 README for Linux 2.6 January 23, 2009 ------------------------------------------------------------------------------- CONTENTS 1.0 About this README file 1.1 Who should read this README file 1.2 How to get help 2.0 Prerequisites for SDD 2.1 Upgrading from previous releases 3.0 SDD Change History 3.1 Defects Fixed 3.1.1 Common 3.1.2 ESS/DS8000/DS6000 Defects 3.1.3 SVC Defects 3.2 New Features 3.3 Feature Details 3.4 Known Issues 3.5 Correction to User's Guide 4.0 User License Agreement for IBM Device Drivers 5.0 Notices 6.0 Trademarks and Service Marks ------------------------------------------------------------------------------- 1.0 About this README file Welcome to IBM System Storage Multipath Subsystem Device Driver (SDD). This README file contains the most recent information about the IBM System Storage Multipath Subsystem Device Driver, Version 1.6.3.0-8 for Linux. IBM recommends that you go to the following Web site to get the most current information about this release of SDD: http://www.ibm.com/servers/storage/support/software/sdd/ You should carefully review the following information available through the website: 1. The most current README file. This will contain corrections to this readme file, corrections to the SDD User's Guide, and other documentation updates discovered since this copy of the README was prepared. 2. The Multipath SDD User's Guide. Because SDD can be installed in so many different environments / configurations, detailed information about each environment is placed in the appropriate chapter of the Multipath SDD Users Guide. The 'Summary of Changes' section of the SDD Users' Guide can help you quickly determine if the latest changes affect you. 3. The Flashes. As we become aware of any information that is likely to impact a broad set of our customers, Flashes are prepared and posted on this site. You should review this section periodocally to see any new Flashes that have been posted since your last review. For prerequisites information, be sure to look in the Multipath SDD User's Guide as well as the prerequisites section of this readme file for the latest updates. For specifics on the hardware and software levels supported by a storage family, please refer to the interoperability information provided by the storage family. 1.1 Who should read this README file This README file is in general intended for storage administrators, system programmers, and performance and capacity analysts. The information in this file only applies to customers who run: 1. DS8000 2. DS6000 3. SAN Volume Controller 4. ESS Please refer to SDD support matrix to determine the supported SDD levels for above storage subsystem. 1.2 How to get help Go to the following Web site for SDD technical support and for the most current SDD documentation and support information: http://www.ibm.com/servers/storage/support/software/sdd/ Go to the following Web site for the IBM ESS Open Systems support: http://www.storage.ibm.com/hardsoft/products/ess/supserver.htm Go to the following Web site for IBM Total Storage DS8000 support: http://www.ibm.com/servers/storage/disk/ds8000/index.html Go to the following Web site for IBM Total Storage DS6000 support: http://www.ibm.com/servers/storage/disk/ds6000/index.html Go to the following Web site for IBM System Storage SAN Volume Controller support: http://www.ibm.com/servers/storage/support/virtual/2145.html Call one of the following numbers to obtain nontechnical or administrative support, such as hardware and software orders, hardware maintenance, services contract of entitlement, and invoices: .For commercial or state and local support operations: 1-877-426-6006 (Listen to the voice prompts) .For business partner support operations: 1-800-426-9990 .For federal government support operations: 1-800-333-6705 ------------------------------------------------------------------------------- 2.0 Prerequisites for SDD One of the following combinations of a Linux distribution and associated vendor compiled binary kernel packages: SuSE SLES 9 (x86) with one of the following kernels: SP2: kernel-smp-2.6.5-7.193 kernel-bigsmp-2.6.5-7.193 kernel-smp-2.6.5-7.201 kernel-bigsmp-2.6.5-7.201 kernel-smp-2.6.5-7.202.7 kernel-bigsmp-2.6.5-7.202.7 SP3: kernel-smp-2.6.5-7.244 kernel-bigsmp-2.6.5-7.244 kernel-smp-2.6.5-7.252 kernel-bigsmp-2.6.5-7.252 kernel-smp-2.6.5-7.257 kernel-bigsmp-2.6.5-7.257 kernel-smp-2.6.5-7.267 kernel-bigsmp-2.6.5-7.267 kernel-smp-2.6.5-7.276 kernel-bigsmp-2.6.5-7.276 kernel-smp-2.6.5-7.282 kernel-bigsmp-2.6.5-7.282 kernel-smp-2.6.5-7.283 kernel-bigsmp-2.6.5-7.283 kernel-smp-2.6.5-7.286 kernel-bigsmp-2.6.5-7.286 kernel-smp-2.6.5-7.287.3 kernel-bigsmp-2.6.5-7.287.3 SP4: kernel-smp-2.6.5-7.305 kernel-bigsmp-2.6.5-7.305 kernel-smp-2.6.5-7.308 kernel-bigsmp-2.6.5-7.308 kernel-smp-2.6.5-7.311 kernel-bigsmp-2.6.5-7.311 kernel-smp-2.6.5-7.312 kernel-bigsmp-2.6.5-7.312 SuSE SLES 9 (ppc64) with one of the following kernels: SP2: kernel-pseries64-2.6.5-7.193 kernel-pseries64-2.6.5-7.201 kernel-pseries64-2.6.5-7.202.7 SP3: kernel-pseries64-2.6.5-7.244 kernel-pseries64-2.6.5-7.252 kernel-pseries64-2.6.5-7.257 kernel-pseries64-2.6.5-7.267 kernel-pseries64-2.6.5-7.276 kernel-pseries64-2.6.5-7.282 kernel-pseries64-2.6.5-7.283 kernel-pseries64-2.6.5-7.286 kernel-pseries64-2.6.5-7.287.3 SP4: kernel-pseries64-2.6.5-7.305 kernel-pseries64-2.6.5-7.308 kernel-pseries64-2.6.5-7.311 kernel-pseries64-2.6.5-7.312 SuSE SLES 9 (x86_64) with one of the following kernels: SP2: kernel-smp-2.6.5-7.193 kernel-smp-2.6.5-7.201 kernel-smp-2.6.5-7.202.7 SP3: kernel-smp-2.6.5-7.244 kernel-smp-2.6.5-7.252 kernel-smp-2.6.5-7.257 kernel-smp-2.6.5-7.267 kernel-smp-2.6.5-7.276 kernel-smp-2.6.5-7.282 kernel-smp-2.6.5-7.283 kernel-smp-2.6.5-7.286 kernel-smp-2.6.5-7.287.3 SP4: kernel-smp-2.6.5-7.305 kernel-smp-2.6.5-7.308 kernel-smp-2.6.5-7.311 kernel-smp-2.6.5-7.312 Red Hat Enterprise Linux 4 (x86) with one of the following kernels: U1: kernel-smp-2.6.9-11.EL kernel-hugemem-2.6.9-11.EL U2: kernel-smp-2.6.9-22.EL kernel-hugemem-2.6.9-22.EL kernel-smp-2.6.9-22.0.1.EL kernel-hugemem-2.6.9-22.0.1.EL kernel-smp-2.6.9-22.0.2.EL kernel-hugemem-2.6.9-22.0.2.EL U3: kernel-smp-2.6.9-34.EL kernel-hugemem-2.6.9-34.EL kernel-smp-2.6.9-34.0.1.EL kernel-hugemem-2.6.9-34.0.1.EL kernel-smp-2.6.9-34.0.2.EL kernel-hugemem-2.6.9-34.0.2.EL U4: kernel-smp-2.6.9-42.EL kernel-hugemem-2.6.9-42.EL kernel-smp-2.6.9-42.0.2.EL kernel-hugemem-2.6.9-42.0.2.EL kernel-smp-2.6.9-42.0.3.EL kernel-hugemem-2.6.9-42.0.3.EL kernel-smp-2.6.9-42.0.8.EL kernel-hugemem-2.6.9-42.0.8.EL kernel-smp-2.6.9-42.0.10.EL kernel-hugemem-2.6.9-42.0.10.EL U5: kernel-smp-2.6.9-55.EL kernel-hugemem-2.6.9-55.EL kernel-smp-2.6.9-55.0.2.EL kernel-hugemem-2.6.9-55.0.2.EL kernel-smp-2.6.9-55.0.6.EL kernel-hugemem-2.6.9-55.0.6.EL kernel-smp-2.6.9-55.0.9.EL kernel-hugemem-2.6.9-55.0.9.EL kernel-smp-2.6.9-55.0.12.EL kernel-hugemem-2.6.9-55.0.12.EL U6: kernel-smp-2.6.9-67.EL kernel-hugemem-2.6.9-67.EL kernel-smp-2.6.9-67.0.1.EL kernel-hugemem-2.6.9-67.0.1.EL kernel-smp-2.6.9-67.0.4.EL kernel-hugemem-2.6.9-67.0.4.EL kernel-smp-2.6.9-67.0.7.EL kernel-hugemem-2.6.9-67.0.7.EL kernel-smp-2.6.9-67.0.15.EL kernel-hugemem-2.6.9-67.0.15.EL kernel-smp-2.6.9-67.0.20.EL kernel-hugemem-2.6.9-67.0.20.EL kernel-smp-2.6.9-67.0.22.EL kernel-hugemem-2.6.9-67.0.22.EL U7: kernel-smp-2.6.9-78.EL kernel-hugemem-2.6.9-78.EL kernel-smp-2.6.9-78.0.1.EL kernel-hugemem-2.6.9-78.0.1.EL Red Hat Enterprise Linux 4 (ppc64) with one of the following kernels: U1: kernel-2.6.9-11.EL U2: kernel-2.6.9-22.EL kernel-2.6.9-22.0.1.EL kernel-2.6.9-22.0.2.EL U3: kernel-2.6.9-34.EL kernel-2.6.9-34.0.1.EL kernel-2.6.9-34.0.2.EL U4: kernel-2.6.9-42.EL kernel-2.6.9-42.0.2.EL kernel-2.6.9-42.0.3.EL kernel-2.6.9-42.0.8.EL kernel-2.6.9-42.0.10.EL U5: kernel-2.6.9-55.EL kernel-2.6.9-55.0.2.EL kernel-2.6.9-55.0.6.EL kernel-2.6.9-55.0.9.EL kernel-2.6.9-55.0.12.EL U6: kernel-2.6.9-67.EL kernel-2.6.9-67.0.1.EL kernel-2.6.9-67.0.4.EL kernel-2.6.9-67.0.7.EL kernel-2.6.9-67.0.15.EL kernel-2.6.9-67.0.20.EL kernel-2.6.9-67.0.22.EL U7: kernel-2.6.9-78.EL kernel-2.6.9-78.0.1.EL Red Hat Enterprise Linux 4 (x86_64) with one of the following kernels: U1: kernel-smp-2.6.9-11.EL U2: kernel-smp-2.6.9-22.EL kernel-smp-2.6.9-22.0.1.EL kernel-smp-2.6.9-22.0.2.EL U3: kernel-smp-2.6.9-34.EL kernel-smp-2.6.9-34.0.1.EL kernel-smp-2.6.9-34.0.2.EL U4: kernel-smp-2.6.9-42.EL kernel-smp-2.6.9-42.0.2.EL kernel-smp-2.6.9-42.0.3.EL kernel-smp-2.6.9-42.0.8.EL kernel-smp-2.6.9-42.0.10.EL U5: kernel-smp-2.6.9-55.EL kernel-smp-2.6.9-55.0.2.EL kernel-smp-2.6.9-55.0.6.EL kernel-smp-2.6.9-55.0.9.EL kernel-smp-2.6.9-55.0.12.EL U6: kernel-smp-2.6.9-67.EL kernel-smp-2.6.9-67.0.1.EL kernel-smp-2.6.9-67.0.4.EL kernel-smp-2.6.9-67.0.7.EL kernel-smp-2.6.9-67.0.15.EL kernel-smp-2.6.9-67.0.20.EL kernel-smp-2.6.9-67.0.22.EL U7: kernel-smp-2.6.9-78.EL kernel-smp-2.6.9-78.0.1.EL * Newly supported in this release. 2.1 Upgrading from previous releases Users upgrading to this release should reboot their machine after installation. Users upgrading from a pre-SDD 1.6.1.x package should NOT use the rpm upgrade command (rpm -U). Instead: 1. Uninstall the SDD package using the RPM erase command: rpm -e IBMsdd 2. Install the new SDD 1.6.1.x or later package: rpm -i 3. If you modified your /etc/vpath.conf, the rpm -e command saved a copy in /etc/vpath.conf.rpmsave. To preserve your /etc/vpath.conf modifications, you must also copy the /etc/vpath.conf.rpmsave to /etc/vpath.conf. ------------------------------------------------------------------------------- 3.0 SDD Change History =============================================================================== 3.1 Defects Fixed 3.1.1 Common 1.6.3.0-8 o sw 4548 Remove fix made in sdd 1.6.3.0-7 which caused performance issue 1.6.3.0-7 o sw 4454 perform checks before reporting "skip unplug vpath" 1.6.3.0-6 o sw 4224 / hursley 86968 dd_select_retry_path should retry previously failed paths 1.6.3.0-5 o sw 4114 / mc 203863 slow open/close performance 1.6.3.0-4 o sw 4102 / mc 203442 / mc 201686 BUG triggered in vpath_close in ps_close.c o sw 4103 / pmr 01745,000,766 vpath_chrdev_read overwriting kernel space memory o sw 4105 replace "wc -l" with "grep -c" in rcscript 1.6.3.0-1 o Incorrect version reported during module load for RHEL 4 distros. o pmr 34178,999 SDD aborts during configuration if any inquiry fails. 1.6.2.0-1 o sw 3937 / mc 181768 Running fdisk with newly created partition on vpath causes system crash 1.6.1.0-4 o sw 3867 / mc 179403 Volume Size incorrect in essmap on x86 archs 3.1.2 ESS defects None 3.1.3 SVC defects None =============================================================================== 3.2 New Features 1.6.1.0-1 o sw 3762/mc 170499 Allow SDD rpm to be installed in other locations besides /opt/IBMsdd. o PCR-2888/OAR-1064 Add support for ESSUTIL. o PCR-2853/OAR-1066 Add support for "datapath clear device count" command to clear SDD vpath device select and error counts. =============================================================================== 3.3 Feature Details 1.6.1.0-1 o sw 3762/mc 170499 Allow SDD rpm to be installed in other locations besides /opt/IBMsdd. For example, to install in /usr: rpm -ivh --prefix=/usr See the SDD User's Guide for more information. o PCR-2888/OAR-1064 Add support for ESSUTIL. See the SDD User's Guide for more information. o PCR-2853/OAR-1066 Add new datapath command to clear Select and/or Error counts as displayed in the "datapath query device" output. Command: datapath clear device n count error/all Syntax: - datapath clear device n count error - datapath clear device n count all - datapath clear device n m count error - datapath clear device n m count all Parameters: - n : The device number that needs its Select/Error count reset. - n m : A range of device numbers whose Select/Error counts need to be reset. - error : Only Error count is reset. - all : Both Select and Error counts are reset. =============================================================================== 3.4 Known Issues o Sddsrv may be removed from /etc/inittab if "sdd stop" is interrupted. o Before creating a partition on a vpath, users must ensure that all of its underlying paths are operational. If there are any offline paths while the partition is being created, running the "fdisk -l" command after the offline paths have been restored could cause a system crash. o Adding vpath entries in /etc/fstab will not mount those devices at boot-up time. If you need to mount vpath devices at boot-up time, follow the automount procedure documented in the User's Guide. o Due to a bug in NFS, vpath devices with minor number > 255, when exported using NFS, will cause mount to hang on the client. To work around this, use the fsid option in /etc/exports. For more details, please refer to the man page, i.e. "man exports". =============================================================================== 3.5 Correction to User's Guide ------------------------------------------------------------------------------ 4.0 User License Agreement for IBM Device Drivers See LICENSE file located in the IBMsdd install directory. ------------------------------------------------------------------------------- 5.0 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services,or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Information Enabling Requests Dept. DZWA 5600 Cottle Road San Jose, CA 95193 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM License Agreement for Non-Warranted Programs. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. =============================================================================== IBM agreement for licensed internal code +---- Read Before Using -----------------------------------------------+ |IMPORTANT | | | |YOU ACCEPT THE TERMS OF THIS IBM LICENSE AGREEMENT FOR MACHINE CODE BY| |YOUR USE OF THE HARDWARE PRODUCT OR MACHINE CODE. PLEASE READ THE | |AGREEMENT CONTAINED IN THIS BOOK BEFORE USING THE HARDWARE PRODUCT.SEE| |IBM agreement for licensed internal code. | | | +----------------------------------------------------------------------+ You accept the terms of this Agreement(3) by your initial use of a machine that contains IBM Licensed Internal Code (called "Code"). These terms apply to Code used by certain machines IBM or your reseller specifies (called "Specific Machines"). International Business Machines Corporation or one of its subsidiaries ("IBM") owns copyrights in Code or has the right to license Code. IBM or a third party owns all copies of Code, including all copies made from them. If you are the rightful possessor of a Specific Machine, IBM grants you a license to use the Code (or any replacement IBM provides) on, or in conjunction with, only the Specific Machine for which the Code is provided. IBM licenses the Code to only one rightful possessor at a time. Under each license, IBM authorizes you to do only the following: 1. execute the Code to enable the Specific Machine to function according to its Official Published Specifications (called "Specifications"); 2. make a backup or archival copy of the Code (unless IBM makes one available for your use), provided you reproduce the copyright notice and any other legend of ownership on the copy. You may use the copy only to replace the original, when necessary; and 3. execute and display the Code as necessary to maintain the Specific Machine. You agree to acquire any replacement for, or additional copy of, Code directly from IBM in accordance with IBM's standard policies and practices. You also agree to use that Code under these terms. You may transfer possession of the Code to another party only with the transfer of the Specific Machine. If you do so, you must 1) destroy all your copies of the Code that were not provided by IBM, 2) either give the other party all your IBM-provided copies of the Code or destroy them, and 3) notify the other party of these terms. IBM licenses the other party when it accepts these terms. These terms apply to all Code you acquire from any source. Your license terminates when you no longer rightfully possess the Specific Machine. Actions you must not take You agree to use the Code only as authorized above. You must not do, for example, any of the following: 1. Otherwise copy, display, transfer, adapt, modify, or distribute the Code (electronically or otherwise), except as IBM may authorize in the Specific Machine's Specifications or in writing to you; 2. Reverse assemble, reverse compile, or otherwise translate the Code unless expressly permitted by applicable law without the possibility of contractual waiver; 3. Sublicense or assign the license for the Code; or 4. Lease the Code or any copy of it. ------------------------------------------------------------------------------- 6.0 Trademarks and service marks The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both: AIX AS/400 Enterprise Storage Server HACMP/6000 IBM IBM logo iSeries Netfinity NetVista Operating System/400 pSeries RS/6000 Seascape SP System/360 System/370 System/390 System Storage The eServer logo Total Storage Versatile Storage Server xSeries zSeries z/Architecture z/OS Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. ------------------------------------------------------------------------------- (C) Copyright IBM Corporation 2000-2006. All rights reserved.