Quantum STORNEXT 3.1.4.1 User Manual

Download

StorNext 3.1.4.1 Release Notes

Product StorNext® 3.1.4.1

Date June 2010

Purpose of This Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Other Changes in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

StorNext End User License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

StorNext Upgrade Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Supported Libraries and Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Minimum Firmware Levels for StorNext Drives . . . . . . . . . . . . . . . . . . . . . . . . 19

Supported System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Resolved Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Quantum, DLT, DLTtape, the Quantum logo, and the DLTtape logo are all registered trademarks of Quantum Corporation. SDLT and Super DLTtape are trademarks of Quantum Corporation. Other trademarks may be mentioned herein which belong to other companies.

StorNext utilizes the following components which are copyrighted by their respective entities:

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Operating Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contacting Quantum . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2 Contents

Purpose of This Release

StorNext 3.1.4.1 is an interim release which addresses previously identified issues and also resolves some critical issues such as the following:

• CR 31271 (SR 1119366): Resolved an issue that could cause data corruption with large mixed data/metadata stripe groups. For more information, refer to StorNext Product Alert 35.

• CR 31272 (SR 1119366): Corrected a condition which resulted in an endless loop when cvfsck reached the point where it writes out the bit map.

• CR 31268 (SR 1113942): Resolved a condition in which using large values for POL_STORE_RESP_ABORT_TIME caused integer overflow. For more information, refer to StorNext Product Alert 34.

• CR 31269 (SR 1113942): File retrieval on SDISK has been enhanced to eliminate errors which prevented retrieving from either copy. For more information, refer to StorNext Product Alert 34.

• CR 31270 (SR 1119366): Corrected an issue in which "fsrmcopy -c ..." failed if the SDISK file was missing.

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

This document also describes supported platforms and system components, as well as currently known issues, issues that were resolved for this release, and known limitations.

Visit www.quantum.com/ServiceandSupport updates for StorNext.

Other Changes in This Release

The delivery mechanism for client software has changed for release 3.1.4.1. Client software for all operating systems is now contained on one disk labeled “Client Software and Product Documentation.” (Formerly, client software was distributed on the software disks for all operating systems.)

As a result of this change, you must now insert the client software disk, copy the client software from the disk, and then install or upgrade the client packages as described in the

In addition, client software is no longer distributed in compressed format (such as tar.gz files). Instead, the client software disk contains executable files which, when launched, extract the client software for the selected platform to the location /tmp/stornext where you can install the package. Windows client packages have not changed, and are still in .zip format.

StorNext 3.1.4.1 Installation Guide

for additional information and

For more information and specific installation instructions, see the

3.1.4.1 Installation Guide

Purpose of This Release 3

StorNext

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

StorNext End User License Agreement

Please read the following StorNext End User License Agreement (EULA). You must read and accept the EULA before you install StorNext.

Quantum Corporation

StorNext End User License Agreement

This License defines the terms and conditions of the license between Quantum Corporation (QUANTUM) and Licensee for use of QUANTUM's Software and Documentation. Any Software or Documentation provided to Licensee by QUANTUM will be subject to the terms and conditions of this License and by downloading, installing or using the Software, Licensee signifies its agreement with this license. If Licensee does not agree to all of the terms of this License, then Licensee must not download, install, or use the Software or Documentation.

1. Definitions:

a “Documentation” means the published documentation accompanying the

Products or available online at QUANTUM’s website, (as applicable) and any Updates thereto, in any form or media provided.

b “Hardware” means the equipment on to which the Software and Open Source

Software is pre-installed or on which it may be installed by Licensee.

c “Open Source Software” means those third party software componen ts identifi ed

as such in the Documentation or in the “About”, “Readme” or similar files in the software, which are required to be licensed under separate terms and conditions by the supplier of such Open Source Software (“ which are delivered as part of the Products and any updates thereto. To obtain a copy of the source code for the Open Source Software, please contact QUANTUM. A copy of the applicable Open Source License is provided with the Open Source Software, in the Documentation, or via the following link on the QUANTUM website:

d “Products” means the Software, Hardware, Open Source Software,

Documentation and maintenance licensed or purchased by Licensee/end-user.

e “Software” means the current version of QUANTUM proprietary software

program(s) accompanying this license, in object code form only, and any updates thereto. Software does not include Open Source Software.

2. Software License.

a License. In consideration of Licensee's payment of the License fees and subject

to the terms of this License, QUANTUM grants to Licensee a personal, nonexclusive, non-transferable license to use the Software and Documentation. A separate license is required for use of each Software program on each of Licensee's computers. The Software will be installed initially on Licensee's Designated Computer. Licensee may thereafter transfer the Software to another one of its computers of the same machine architecture, provided that the Software is installed on one (1) Designated Computer at a time. Licensee acknowledges that Open Source Software is licensed separately pursuant to the applicable Open Source License. Licensee’s use of any Open Source Software shall be subject to and Licensee agrees to comply with the applicable restrictions and other terms and conditions of the applicable Open Source License.

www.quantum.com/OpenSource.

Open Source License”) and

4 StorNext End User License Agreement

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

b Use. Licensee is authorized hereby to use the Software on one computer only

(Designated Computer), or on backup equipment if the Designated Computer is inoperative until such time as the Designated Computer is restored to operation. This grant is specifically limited to use by the Licensee for normal, customary internal data processing, and specifically excludes Licensee's time-sharing or the rental of the Software or use of the Software in the development or marketing of a competitive or compatible product. No right to use, print, copy or display the Software or Documentation, in whole or in part, is granted hereby except as expressly provided in this License.

c Copying. Licensee may make one (1) copy of the Software in a non-printed,

machine-readable form for archival and backup purposes only, and copy the Documentation as needed for internal use only of licensed Software. In order to protect QUANTUM's trade secret and copyrights in the Software and Documentation, Licensee agrees to reproduce and incorporate QUANTUM's trade secret or copyright notice in any copy or partial copy, and will maintain appropriate records of the location of such copy.

d US Government Rights. If the Licensee is the United States government,

Licensee understands and agrees that the Software and Documentation are provided as "Commercial Items" as defined at 48 CFR 2.101 and are being licensed to U.S. Government end users consistent with 48 CFR 12.212 and DFAR Section 227.7202, as applicable.

3. Software Ownership and Protection

a Title to Software. The Software, Documentation, and all copies thereof are

proprietary to QUANTUM and title thereto remains in QUANTUM. All applicable rights to patents, copyrights, trademarks, trade secrets or other proprietary rights in the Software and Documentation and any modifications made at Licensee's request are and will remain in QUANTUM.

b Restrictions. Licensee will not itself or permit others to:

i. sell, sublicense, transfer, publish, disclose, display, provide access via a

network or otherwise make available the Software or Documentation or any copy thereof to others;

ii. remove, obscure, or alter any copyright, trade secret, trademark, patent or

other proprietary rights notice affixed to or displayed on the Software or Documentation;

iii. modify, merge with other programs or translate any portion of the Software

or Documentation into any other assembly or language; and

iv. reverse-assemble, reverse-compile or attempt to derive a source code

equivalent of the Software provided that if you need information in order to assist in debugging a modified Open Source Software library, contact Quantum for assistance.

c Protections. Licensee agrees to secure and protect the Software, the

Documentation, and copies thereof in a manner consistent with QUANTUM's rights therein and to take appropriate action to satisfy its obligations in this Agreement by instruction or agreement with its employees, agents, subcontractors or others who are permitted access to the Software and Documentation. All programs or copies developed by or for Licensee in violation of this License, including translations, compilations, partial copies and updates, are owned by QUANTUM.

StorNext End User License Agreement 5

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

d Responsibility. Licensee has sole responsibility for use of the Products and any

information entered, used, or stored thereon, including responsibility for protection of data from modification, destruction, or disclosure, and for the accuracy and integrity of the data. QUANTUM assumes no responsibility for Licensee's negligence or failure to protect its data.

4. Warranty and Warranty Servicing.

a Warranty. QUANTUM warrants that for a period of 90 days from installation the

Software will conform to all substantial operational features in QUANTUM's current published specifications and will be free of material defects which substantially affect performance of the Software. QUANTUM does not warrant that the Software will meet the Licensee’s requirements or that the operation of the Software will be uninterrupted or error free. The Licensee must notify QUANTUM in writing, within 90 days after installation of the Software of Licensee’s claim of any defect. If QUANTUM determines that the Software is defective, QUANTUM’s sole obligation is for QUANTUM, at its option, to correct, any defect in the Software or to accept the return of the Software. Where Software is returned for claims made during the warranty period, Licensee will receive a refund for the Software. This warranty is made void if the Licensee or any third party makes any modifications to the Software. QUANTUM is not responsible for corrections necessitated by difficulties or defects traceable to Licensee's errors or system changes QUANTUM will have no obligation for the correction of errors that are due to a breach by Licensee of the terms of the Agreement, or that cannot be remedied due to the way Hardware on which the Software or Open Source Software is operated if such Hardware does not meet the minimum systems requirements specified in the Documentation, or as a result of any modifications to the Software or Open Source Software made by Licensee.

b Compatibility. QUANTUM does not warrant that the Software is compatible

with the current releases of all operating systems, nor that the Software will be made compatible with new releases of operating systems within a specified amount of time, or at all. At Licensee's request, QUANTUM will notify Licensee of the version level of the operating system with which the Software is intended to be compatible.

c Warranty Disclaimer. EXCEPT FOR THE EXPRESS LIMITED WARRANTY

STATED ABOVE, THE SOFTWARE AND DOCUMENTATION ARE PROVIDED “AS IS” AND QUANTUM MAKES NO WARRANTIES, EXPRESS OR IMPLIED, FOR THE SOFTWARE OR DOCUMENTATION, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

5.Term and Termination. This License commences on the Effective Date and will

continue uninterrupted unless Licensee fails to comply with any conditions of this License. If Licensee breaches, QUANTUM may, after allowing Licensee a reasonable time to cure its default, terminate this License upon written notice to the Licensee. Within 30 days after termination of this License, Licensee will certify, in writing, to QUANTUM, that Licensee has discontinued the use of all Software and returned to QUANTUM the original and all copies of the Software and Documentation in any form maintained by Licensee.

6 StorNext End User License Agreement

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

6.DISCLAIMER AND LIMITATION OF LIABILITY. THE LICENSEE HAS THE

SOLE RESPONSIBILITY FOR THE ADEQUATE PROTECTION AND BACK-UP OF ITS DATA USED IN CONNECTION WITH THE PRODUCTS. IN NO EVENT WILL QUANTUM BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, RERU N TI ME, INACCURA TE INPUT OR WORK DELAYS, OR ANY PERSONAL OR PROPERTY DAMAGE ARISING OUT OF OR IN CONNECTION WITH THIS LICENSE OR THE USE, PERFORMANCE OR NON-PERFORMANCE OF THE PRODUCTS, WHETHER IN ACTION, IN CONTRACT, OR TORT INCLUDING NEGLIGENCE, EVEN IF QUANTUM KNEW , SHOULD HAVE KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. QUANTUM's LIABILITY FOR DAMAGES HEREUNDER WILL IN NO EVENT EXCEED THE AMOUNT OF FEES PAID BY LICENSEE UNDER THIS LICENSE.

7. General.

a No Assignment or Modification. This License is not assignable. None of the

Software or Documentation may be sublicensed, assigned, or transferred to any other party without QUANTUM’s prior written consent. Any effort contradictory with this is null and void. This License can only be modified by a written agreement executed by the parties.

b Governing Law and Venue. The laws of the state of Washington will govern this

license. All litigation between the parties, including all applications for injunctive relief, must be conducted before a court of competent jurisdiction in King County, Washington, USA and both parties consent to personal jurisdiction of such court. If any of the provisions of this License are held to be invalid under any applicable statute or law, they are, to that extent, deemed omitted.

c Entirety. The laws of the state of Washington will govern this license. All

litigation between the parties, including all applications for injunctive relief, must be conducted before a court of competent jurisdiction in King County, W ashington, USA and both parties consent to personal jurisdiction of such court. If any of the provisions of this License are held to be invalid under any applicable statute or law, they are, to that extent, deemed omitted.

StorNext Upgrade Recommendations

Whenever possible, StorNext systems should run the latest StorNext-supported operating system service pack or update level.

For the 3.1.4.1 release there are no additional upgrade recommendations.

StorNext Upgrade Recommendations 7

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Configuration Requirements

Before installing StorNext 3.1.4.1, note the following configuration requirements:

• In cases where gigabit networking hardware is used and maximum StorNext performance is required, a separate, dedicated switched Ethernet LAN is recommended for the StorNext metadata network. If maximum StorNext performance is not required, shared gigabit networking is acceptable.

• A separate, dedicated switched Ethernet LAN is mandatory for the metadata network if 100 Mbit/s or slower networking hardware is used.

• StorNext does not support file system metadata on the same network as iSCSI, NFS, CIFS, or VLAN data when 100 Mbit/s or slower networking hardware is used.

• The operating system on the metadata controller must always be run in U.S. English.

• For Windows systems (server and client), the operating system must always be run in U.S. English.

Caution: If a Library used by StorNext Storage Manager is connected via a

fibre switch, zone the switch to allow only the system(s) running SNSM to have access to the library. This is necessary to ensure that a “rogue” system does not impact the library and cause data loss or corruption. For more information, see StorNext Product Alert 16 Rev B.

This section contains the following configuration requirement topics:

• Library Requirements

• Disk Requirements

• Disk Naming Requirements

• SAN Disks on Windows Server 2008

Library Requirements The following libraries require special configurations to run StorNext.

DAS and Scalar DLC Network-Attached Libraries

Prior to launching the StorNext Configuration Wizard, DAS, and Scalar DLC network-attached libraries must have the DAS client already installed on the appropriate host control computer.

DAS Attached Libraries

For DAS attached libraries, refer to “Installation and Configuration” and “DAS Configuration File Description” in the

Guide

. The client name is either the default StorNext server host name or the

name selected by the administrator.

8 Configuration Requirements

DAS Installation and Administration

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

StorNext can support LTO-3 WORM media in DAS connected libraries, but WORM media cannot be mixed with other LTO media types in one logical library.

To use LTO-3 WORM media in a logical library, before configuring the library in StorNext, set the environmental variable XDI_DAS_MAP_LTO_TO_LTOW in the /usr/adic/MSM/config/envvar.config file to the name of the library. The library name must match the name given to the library when configuring it with StorNext. If defining multiple libraries with this environmental variable, separate them with a space. After setting the environmental variable, restart StorNext Storage Manager (SNSM).

Note: SDLC software may not correctly recognize LTO-3 WORM media in the

library and instead set it to “unknown media type.” In this case you must manually change the media type to “LTO3” using the SDLC GUI.

Scalar DLC Attached Libraries

For Scalar 10K and Scalar 1000 DLC attached libraries, refer to “Installation and Configuration” and “Client Component Installation” in the

Library Controller Reference Manual

(6-00658-04).

Scalar Distributed

The DAS client should be installed during the installation of the Scalar DLC attached libraries. Use this procedure to install the DAS client.

1 Select Clients > Create DAS Client.

The client name is either the default StorNext server host name or the name selected by the administrator.

2 When the DAS client is configured in Scalar DLC, select Aliasing.

3 Select sony_ait as the Media aliasing. 4 The default value is 8mm.

5 Verify that Element Type has AIT drive selected.

6 Click Change to execute the changes.

ACSLS Attached Libraries

Due to limitations in the STK ACSLS interface, StorNext supports only single ACS configurations (ACS 0 only).

Scalar i500 (Firmware Requirements)

For Scalar i500 libraries that do not have a blade installed, the library and drives must meet the following minimum firmware requirements. (These requirements apply

only

to Scalar i500 libraries that do not have a blade installed.)

• Scalar i500 minimum firmware level: 420GS.GS00600

• HP LTO-4 Fibre/SAS tape device minimum firmware level: H35Z

Caution: If you do not meet the minimum firmware requirements, you

might be unable to add a library to the Scalar i500 using the StorNext Configuration Wizard.

Configuration Requirements 9

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Disk Requirements Disk devices must support, at minimum, the mandatory SCSI commands for

block devices as defined by the SCSI Primary Commands-3 standard (SPC-3) and the SCSI Block Commands-2 (SBC-2) standard.

To ensure disk reliability, Quantum recommends that disk devices meet the requirements specified by Windows Hardware Quality Labs (WHQL) testing. However, there is no need to replace non-WHQL certified devices that have been used successfully with StorNext.

Disk devices must be configured with 512-byte or 4096-byte sectors, and the underlying operating system must support the device at the given sector size. StorNext customers that have arrays configured with 4096-byte sectors can use only Windows, Linux and IRIX clients. Customers with 512-byte arrays can use clients for any valid StorNext operating system (i.e., Windows, Linux, or UNIX).

In some cases, non-conforming disk devices can be identified by examining the output of cvlabel –vvvl. For example:

/dev/rdsk/c1d0p0: Cannot get the disk physical info.

If you receive this message, contact your disk vendors to determine whether the disk has the proper level of SCSI support.

Disk Naming Requirements

SAN Disks on Windows Server 2008

When naming disks, names should be unique across all SANs. If a client connects to more that one SAN, a conflict will arise if the client sees two disks with the same name.

SAN policy has been introduced in Windows Server 2008 to protect shared disks accessed by multiple servers. The first time the server sees the disk it will be offline, so StorNext is prevented from using or labeling the disk.

To bring the disks online, use the POLICY=OnlineAll setting. If this doesn’t set the disks online after a reboot, you may need to go to Windows Disk Management and set each disk online.

Follow these steps to set all disks online:

1 From the command prompt, type DISKPART

2 Typ e SAN to view the current SAN policy of the disks.

3 To set all the disks online, type SAN POLICY=onlineall.

4 After being brought online once, the disks should stay online after

rebooting.

5 If the disks appear as “Not Initialized” in Windows Disk Management after a

reboot, this indicates the disks are ready for use.

If the disks still appear as offline in Disk Management after rebooting, you must set each disk online by right-clicking the disk and selecting Online. This should always leave the SAN disks online after reboot.

Note: NOTE: If the disks are shared among servers, above steps may lead to

data corruption. Users are encouraged to use the proper SAN policy to protect data

10 Configuration Requirements

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

EXAMPLE:

C:\ >Diskpart Microsoft DiskPart version 6.0.6001 Copyright (C) 1999-2007 Microsoft Corporation. On computer: CALIFORNIA DISKPART> SAN SAN Policy : Offline All DISKPART> san policy=onlineall DiskPart successfully changed the SAN policy for the current operating system.

Configuration Requirements 11

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Operating System Requirements

Tab l e 1 shows the operating systems, kernel versions, and hardware platforms

that support StorNext File System, StorNext Storage Manager, and the StorNext client software.

This table also indicates the platforms that support the following:

•MDC Servers

• Distributed LAN Servers

• File System LAN Clients

Table 1 StorNext Supported OSes and Platforms

Notes: When adding StorNext Storage Manager to a StorNext File System environment, the

metadata controller (MDC) must be moved to a supported platform. If you attempt to install and run a StorNext 3.1.4.1 server that is not supported, you do so at your own risk. Quantum strongly recommends against installing non-supported servers.

* 64-bit versions of Windows support up to 128 distributed LAN clients. 32-bit versions of

Windows are not recommended for MDC server or Distributed LAN due to memory limitations.

12 Operating System Requirements

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Notes:

†

All releases of RHEL4 and RHEL5 except RHEL4 Update 8 and RHEL5 Update 4 have a possible

silent data corruption issue as documented in Product Alert #20. Quantum recommends that users migrate to RHEL4 Update 8 or RHEL5 Update 4 as soon as possible. Also, note that the "Xen" virtualization software is not supported for RHEL 4 and RHEL 5.

††

SLES 10 SP1 (and earlier) and SP2 kernels earlier than 37 are sensitive to the same silent data corruption issue documented in Product Alert #20. The problem has been fixed in SP2 that includes level 2.6.16.60-0.37_f594963d, in SLES 10 SP3, and in the SLES 11 releases. There is no recommended workaround at this time.

‡

HBA multipath customers: please verify with your HBA vendor that your current multipath driver is supported for any planned Linux OS version/update/service pack level. If your driver is not supported for your planned Linux OS version/update/service pack, the StorNext client or server may not be functional after your Linux upgrade.

***

A "roll" of a particular digit is not indicative that a new SLES service pack has been declared by Novell. The kernel revisions listed in this document are typically (but not always), the first kernel revision of the service pack. Later revisions within the service pack are typically supported.

Operating System Requirements 13

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Note: For systems running Red Hat Enterprise Linux version 4 or 5, before

installing StorNext you must first install the kernel header files (shipped as the kernel-devel-smp or kernel-devel RPM).

For systems running SUSE Linux Enterprise Server, you must first install the kernel source code (typically shipped as the kernel-source RPM).

Caution: Red Hat 5 ships with secure Linux kernel enabled by default. To

ensure proper StorNext operation, you must not install Red Hat 5 with secure Linux enabled. The secure Linux kernel must be off, or the file system could fail to start.

Note: GNU tar is required on Solaris systems. In addition, for systems running

Solaris 10, install the Recommended Patch Cluster (dated March 10, 2006 or later) before installing StorNext.

To e n ab l e s u pp o rt f or LU N s g r e a ter than 2TB on Solaris 10, the following patches are required:

• 118822-23 (or greater) Kernel Patch

• 118996-03 (or greater) Format Patch

• 119374-07 (or greater) SD and SSD Patch

• 120998-01 (or greater) SD Headers Patch

14 Operating System Requirements

Supported Libraries and Tape Drives

Libraries and tape drives supported for use with StorNext 3.1.4.1 are presented in Tab l e 2

Table 2 StorNext Supported Libraries and Tape Drives

. Where applicable, minimum firmware levels for libraries are provided.

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Supported Libraries and Tape Drives 15

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

16 Supported Libraries and Tape Drives

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Note 1: The Sun / StorageTek FC and ACSLS sections have been modified to include drive and

library permutations that are "paper certified" based on testing that has been performed and validated by Sun/STK.

Note 2: Tape cleaning problem introduced with 1.38.209, special fix at RA1.38.209. 1.40.x

firmware level where fix was rolled forward has not been determined yet.

Note 3: When using T10000 drives, the STK library parameter "Fastload" must be set to "OFF".

Note 4: Minimum: RA1.38.209, but note that 1.38.209 manifests tape cleaning issue, recently

tested: 1.40.208 (with tape cleaning failure).

Supported Libraries and Tape Drives 17

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Note 1: The Sun / StorageTek FC and ACSLS sections have been modified to include drive and

library permutations that are "paper certified" based on testing that has been performed and validated by Sun/STK.

Note 2: Tape cleaning problem introduced with 1.38.209, special fix at RA1.38.209. 1.40.x

firmware level where fix was rolled forward has not been determined yet.

Note 3: When using T10000 drives, the STK library parameter "Fastload" must be set to "OFF".

Note 4: Minimum: RA1.38.209, but note that 1.38.209 manifests tape cleaning issue, recently

tested: 1.40.208 (with tape cleaning failure).

18 Supported Libraries and Tape Drives

StorNext 3.1.4.1 Release Notes

Minimum Firmware Levels for StorNext Drives

Where applicable, the minimum firmware levels for StorNext-supported drives are shown in Ta b l e 3

Table 3 Minimum Firmware Levels for Drives

6-00431-29 Rev A

June 2010

Note: When using IBM Ultrium-TD3 drives with SUSE Linux Enterprise Server 10, you must upgrade the drive firmware to version 64D0 or later.

Supported System Components

System components that are supported for use with StorNext 3.1.4.1 are presented in Tab l e 4

Table 4 StorNext Supported System Components

Component Description

Browsers Internet Explorer 6.0 or later (including 7.0)

Mozilla Firefox 1.5 or later (including 2.0 or later) (Minimum browser resolution: 800x600)

NOTE: Disable pop-up blockers.

Minimum Firmware Levels for StorNext Drives 19

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Component Description

LTO- 1 Media t o LTO- 3 or LTO - 4 Driv e Compatibility

NFS Version 3

LTO-1 media in an LTO-3 or LTO-4 library (LTO-3 or LTO-4 drives) are considered for store requests unless they are logically marked as write protected. When LTO- 1 media i s moun t ed in a n LTO- 3 or LTO - 4 driv e, StorNext marks the media as write protected. Quantum recommends circumventing LTO-1 media for store requests by following this procedure:

1 From the SNSM home page, choose Attributes

from the Media menu.

2 On the Change Media Attributes window, select

the LTO - 1 media from the list.

3 Click the Write Protect option. 4 Click Apply to make the change. 5 Repeat the process for each piece of LTO-1 media.

NOTE: An NFS server that exports a StorNext file

system with the default export options may not flush data to disk immediately when an NFS client requests it. This could result in loss of data if the NFS server crashes after the client has written data, but before the data has reached the disk.

This issue will be addressed in a future StorNext

release. As a workaround, add the no_wdelay option to each line in the /etc/exports file that references a

StorNext file system. For example, typical export

options would be (rw,sync,no_wdelay).

Addressable Power Switch

LDAP LDAP (Lightweight Directory Access Protocol) support

Hardware Requirements

To successfully install StorNext 3.1.4.1, the following hardware requirements must be met:

• StorNext File System and Storage Manager Requirements

• StorNext Client Software Requirements

WTI RPS-10m WTI IPS-800

The RPS-10m (master) is supported. The RPS-10s (slave) is not supported.

requires Windows Active Directory.

20 Hardware Requirements

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Note: The following requirements are for running StorNext only. Running

additional software (including the StorNext client software) requires additional RAM and disk space.

StorNext File System and Storage Manager Requirements

Table 5 File System and Storage Manager Hardware Requirements

The hardware requirements for StorNext File System and Storage Manager are presented in Tab l e 5

No. of File Systems

RAM File System Disk Space

Storage Manager Disk Space

1–4* 2 GB 2 GB • For application

5–8** 4 GB 4 GB

binaries, log files, and documentation: up to 30GB (depending on system activity)

• For support directories: 3 GB per million files stored

* Two or more CPU cores are recommended for best performance. ** Two or more CPU cores are required for best performance.

StorNext Client Software Requirements

Note: If a file system uses deduplicated storage disks (DDisks), note the

following additional requirements:

• Requires 2 GB RAM per DDisk in addition to the base RAM noted in

Tab l e 5 .

• Requires an additional 5GB of disk space for application binaries and log files.

• Deduplication is supported only for file systems running on a Linux operating system.

• An Intel Pentium 4 or later processor (or an equivalent AMD processor) is required. For best performance, Quantum recommends an extra CPU per DDisk.

To install and run the StorNext client software, the client system must meet the following minimum hardware requirements.

For SAN (FC-attached) clients or for Distributed LAN Clients:

•1 GB RAM

Hardware Requirements 21

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Resolved Issues

• 500 MB available hard disk space

For SAN clients acting as a Distributed LAN Server:

•2 GB RAM

• 500 MB available hard disk space

Note: Distributed LAN servers may require additional RAM depending on the

number of file systems, Distributed LAN Clients, and NICs used. See

Distributed LAN Server Memory Tuning in the StorNext User’s Guide for

Distributed LAN Server memory tuning guidelines.

The following sections list resolved issues in this release of StorNext:

• StorNext File System Resolved Issues on page 22

• StorNext Storage Manager Resolved Issues on page 23

• StorNext GUI Resolved Issues on page 23

• StorNext Installation and Database Resolved Issues on page 24

Note: There is no change to cryptographic functionality in StorNext release

3.1.4.1.

StorNext File System

Tab l e 6 lists resolved issues that are specific to StorNext File System.

Resolved Issues

Table 6 StorNext File System Resolved Issues

Change Operating System

Windows 31274 n/a An updated end user license agreement (EULA) has been

Request

Number

Service Request Number

Description

incorporated into the Windows installer.

All 31271 1119366 Resolved an issue that could cause data corruption with large

mixed data/metadata stripe groups.

31272 1119366 Corrected a condition which resulted in an endless loop when

cvfsck reached the point where it writes out the bit map.

22 Resolved Issues

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

StorNext Storage

Tab l e 7 lists resolved issues that are specific to StorNext Storage Manager.

Manager Resolved Issues

Table 7 StorNext Storage Manager Resolved Issues

Operating System

Change

Request

Number

Service Request Number

Description

All 31268 1113942 Resolved a condition in which using large values for

POL_STORE_RESP_ABORT_TIME caused integer overflow.

31269 1113942 File retrieval on SDISK has been enhanced to eliminate errors which

prevented retrieving from either copy.

31270 1119366 Corrected an issue in which "fsrmcopy -c ..." failed if the SDISK file

was missing.

StorNext GUI Resolved

Tab l e 8 lists resolved issues that are specific to the StorNext GUI.

Issues

Table 8 StorNext GUI Resolved Issues

Operating System

Change

Request

Number

Service Request Number

Description

All 31275 n/a Before client installation files can be extracted, the StorNext end

user license agreement must first be read and accepted.

Resolved Issues 23

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

StorNext Installation and Database Resolved

Tab l e 9 lists resolved issues that are specific to StorNext installation and the

database.

Issues

Table 9 StorNext Installation and Database Resolved Issues

Change Operating System

Request

Number

All 31273 n/a The StorNext end user license agreement is now presented during

Service Request Number

Description

the installation process.

24 Resolved Issues

Known Issues

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

The following sections list known issues in this release of StorNext, as well as associated workarounds, where applicable:

• StorNext File System Known Issues on page 25

• StorNext Storage Manager Known Issues on page 28

• StorNext Installation Known Issues on page 29

StorNext File System

Tab l e 1 0 lists known issues that are specific to StorNext File System.

Known Issues

Table 10 StorNext File System Known Issues

Change Operating System

Linux 23661 958244 StorNext File System does not

Request

Number

24890 836284 DMA I/Os may hang when the

Service Request Number

Description Workaround

support the Linux sendfile() system call.

This issue causes Apache web servers to deliver blank pages when content resides on StorNext file systems.

This issue also affects Samba servers running on Linux.

file offset is not aligned and disks configured with 4096-byte sectors are used. For example:

dd if=/stornext/ sr83628a/file2g of=/dev/ null bs=1880000 count=1 skip=40

The workaround is to disable sendfile usage by adding the following entry into the Apache configuration file

EnableSendfile off

The workaround for Samba servers is to add the following line into the configuration file:

sendfile=no

This issue will be addressed in a future StorNext release.

As a workaround, use the “memalign=4k” mount option.

Note: this mount option should NOT be used with file systems containing LUNs configured with 512-byte sectors.

httpd.conf:

Known Issues 25

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Operating System

Change

Request

Number

Service Request Number

Description Workaround

Linux 25102 n/a 32-bit StorNext Distributed

Gateways may lock up under load. This problem is due to “highmem” kernel memory depletion and occurs under load when several distributed LAN clients perform I/O concurrently. Using a larger than default value for the transfer_buffer_size_kb parameter in the dpserver file will exacerbate the problem.

25864 n/a An NFS server that exports a

StorNext file system with the default export options may not flush data to disk immediately when an NFS client requests it. This could result in loss of data if the NFS server crashes after the client has written data, but before the data has reached the disk.

The workaround is to use 64-bit Distributed Gateways.

This issue will be addressed in a future StorNext release.

As a workaround, add the no_wdelay option to each line in the /etc/exports file that references a StorNext file system. For example, typical export options would be (rw,sync,no_wdelay).

26321 n/a Due to the way Linux handles

errors, the appearance of SCSI “No Sense” messages in system logs can indicate possible data corruption on disk devices.

This affects StorNext users on Red Hat 4, Red Hat 5, and SuSe

10.

This issue is not caused by StorNext, and is described in detail in StorNext Product Alert 20.

For additional information, see Red Hat 5 CR 468088 and SuSE 10 CR

10440734121.

26 Known Issues

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Operating System

Change

Request

Number

Service Request Number

Description Workaround

Windows 25032 n/a If you are using Promise RAID

controllers on a Windows Server 2008 64-bit system, you must install Promise’s PerfectPath software. (PerfectPath also helps recognize multiple-path failovers.)

If you do not install this software, you will be unable to use your Windows Server 2008 system.

Promise is working on a solution to this problem, but in the meantime they have provided the following workaround:

1. Install the PerfectPath software on your Windows Server 2008 64bit system.

2. Restart your system. The login prompt will

not

appear after you

restart. Instead, the Windows Boot Manager screen appears showing an error message: “Windows cannot verify the digital signature for this file” (\Windows\system32\DRIVERS

\ perfectpathdsm.sys)

3. From the Windows Boot Manager screen, press Enter to continue. A second Windows Boot Manager screen appears, asking

you to choose an operating system or specify an advanced option.

4. On the second Windows Boot Manager screen, press F8 to specify advanced options. The Advanced Boot Options screen appears.

5. On the Advanced Boot Options screen, use the arrow keys to choose the option Disable Driver Signature Enforcement. Choosing this option will cause the system to display the login prompt normally after you reboot.

6. Restart your system.

Known Issues 27

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

StorNext Storage

Tab l e 1 1 lists known issues that are specific to StorNext Storage Manager.

Manager Known Issues

Table 11 StorNext Storage Manager Known Issues

Change Operating System

Request

Number

Windows 23974 756992,

All 25766 870012,

25837 836242 Running fsmedcopy fails if the

Service Request Number

927644

886856

Description Workaround

TSM-Files having a group name longer than ten characters can

This issue will be addressed in a

future StorNext release. cause poor fs_fmover response, and could cause immediate file truncation failure.

MSM failed to start with “glibc double free or corruption”

This issue will be addressed in a

future StorNext release.

The workaround is to remove

outstanding MSM requests stored

in the Request table.

This issue will be addressed in a output medium does not have sufficient space to hold the copies from the input.

However, the copies successfully transferred to the new media

future StorNext release.

As a workaround, a few

fsmedcopy runs will get all the

files from the larger input media to

the new (smaller) media. can be identified with the fsfileinfo command.

28 Known Issues

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

StorNext Installation

Tab l e 1 2 lists known issues that are specific to the StorNext installation process.

Known Issues

Table 12 StorNext Installation Known Issues

Change Operating System

Linux

Request

Number

24692 n/a When you mount a CD in a Red (RHEL4 and RHEL5 only)

Windows 27129 n/a An incompatibility between

Service Request Number

Description Workaround

Hat 4 or 5 system, CDs are mounted by default with a noexec (non-executable) option which prevents you from proceeding with the StorNext

installation.

StorNext 3.1.2, 3.1.3 and 3.5 installers and Altiris Agent running as a service (C:\Program Files\

Altiris\Altiris Agent\ AeXNSAgent.exe) could cause

the StorNext installation to fail.

Remount the CD by typing mount

-o remount, exec ...

Alternatively, mount the CD to a different directory by typing the following:

# mkdir /mnt/MOUNT_PATH # mount /dev/cdrom /mnt/ MOUNT_PATH # cd /mnt/ MOUNT_PATH

This issue will be addressed in a future StorNext release.

To avoid encountering this issue, disable the Altiris Agent service before installing StorNext.

Known Issues 29

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Operating Guidelines and Limitations

Tab l e 1 3 lists updated information and guidelines for running StorNext, as well

as known limitations in this release.

Table 13 StorNext Operating Guidelines and Limitations

Operating System / Affected Component

Windows When a StorNext file system is mounted to a drive letter or a

Description

directory, configure the Windows backup utility to NOT include the StorNext file system.

If you are using the StorNext client software with Windows Server 2003, Windows Server 2008, Windows XP, or Windows Vista, turn off the Recycle Bin in the StorNext file systems mapped on the Windows machine.

You must disable the Recycle Bin for the drive on which a StorNext file system is mounted. Also, each occurrence of file system remapping (unmounting/mounting) will require disabling the Recycle Bin. For example, if you mount a file system on E: (and disable the Recycle Bin for that drive) and then remap the file system to F:, you must then disable the Recycle Bin on the F: drive.

As of release 3.5, StorNext supports mounting file systems to a directory. For Windows Server 2003 and Windows XP you must disable the Recycle Bin for the root drive letter of the directorymounted file system. (For example: For C:\MOUNT\File_System you would disable the Recycle Bin for the C: drive.) For Windows Server 2008 and Windows Vista you must disable each directorymounted file system.

For Windows Server 2003 or Windows XP: 1 On the Windows client machine, right-click the Recycle Bin icon

on the desktop and then click Properties.

2 Click Global. 3 Click Configure drives independently. 4 Click the Local Disk tab that corresponds to the mapped or

directory-mounted file system.

5 Click the checkbox Do not move files to the Recycle Bin. Remove files

immediately when deleted

6 Click Apply, and then click OK.

30 Operating Guidelines and Limitations

StorNext 3.1.4.1 Release Notes

6-00431-29 Rev A

June 2010

Operating System / Affected Component Description

Windows For Windows Server 2008 and Windows Vista:

1 On the Windows client machine, right-click the Recycle Bin icon

on the desktop and then click Properties.

2 Click the General tab. 3 Select the mapped drive that corresponds to the StorNext mapped

file system. For directory-mounted file systems, select the file system from the list.

4 Choose the option Do not move files to the Recycle Bin. Remove files

immediately when deleted

5 Click Apply. 6 Repeat steps 3-5 for each remaining directory-mounted file system. 7 When finished, click OK.

All Be aware of the following limitations regarding file systems and

stripe groups:

• The maximum number of disks per file system is 512

• The maximum number of disks per data stripe group is 128

• The maximum number of stripe groups per file system is 256

• The maximum number of tape drives is 256

Documentation

For managed file systems only, the recommended maximum directory capacity is 50,000 files per single directory. (This limitation does not apply to unmanaged file systems.)

If you use an SDisk or DDisk, you should save at least one other copy of the data to tape or to another SDisk or Ddisk. Without the second copy, your stored data will be vulnerable to data loss if you ever have hardware failure.

The following documents are currently available for StorNext products:

Document Number Document Title

6-01658-08 StorNext User’s Guide

6-00360-17 StorNext Installation Guide

6-01376-12 StorNext File System Tuning Guide

6-01620-11 StorNext Upgrade Guide

6-01688-08 StorNext CLI Reference Guide

6-00361-33 StorNext File System Quick Reference Guide

Documentation 31

StorNext 3.1.4.1 Release Notes 6-00431-29 Rev A June 2010

Document Number Document Title

6-00361-34 StorNext Storage Manager Quick Reference Guide

Contacting Quantum

More information about this product is available on the Service and Support website at www.quantum.com/support contains a collection of information, including answers to frequently asked questions (FAQs). You can also access software, firmware, and drivers through this site.

For further assistance, or if training is desired, contact Quantum:

United States 800-284-5101 (toll free)

. The Service and Support Website

949-725-2100

Worldwide End-User Product Warranty

EMEA 00800-4-782-6886 (toll free)

+49 6131 3241 1164

APAC +800 7826 8887 (toll free)

+603 7953 3010

For worldwide support:

http://www.quantum.com/ServiceandSupport/Index.aspx

For more information on the Quantum Worldwide End-User Standard Limited Product Warranty:

http://www.quantum.com/pdf/QuantumWarranty.pdf

32 Contacting Quantum

Quantum STORNEXT 3.1.4.1 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Purpose of This Release

Other Changes in This Release

StorNext End User License Agreement

StorNext Upgrade Recommendations

Configuration Requirements

• Library Requirements

DAS and Scalar DLC Network-Attached Libraries

DAS Attached Libraries

Scalar DLC Attached Libraries

ACSLS Attached Libraries

Scalar i500 (Firmware Requirements)

Disk Requirements Disk devices must support, at minimum, the mandatory SCSI commands for

Disk Naming Requirements

SAN Disks on Windows Server 2008

Operating System Requirements

Supported Libraries and Tape Drives

Minimum Firmware Levels for StorNext Drives

Supported System Components

Hardware Requirements

StorNext File System and Storage Manager Requirements

StorNext Client Software Requirements

Resolved Issues

• StorNext File System Resolved Issues on page 22

Known Issues

• StorNext File System Known Issues on page 25

Operating Guidelines and Limitations

Documentation

Contacting Quantum