HP IBRIX X9000 Storage 6.1.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Version: 6.1.4 (build 6.1.310) Description Update eligibility Customers running IBRIX OS Software 6.1.x, 6.0.x, 5.6.x, 5.5.x, or 5.4.x are eligible for the update. Refer to the administrator guide for your storage system for specific update requirements and procedures. Customers running X9000 File Serving Software 5.3.2 or earlier versions should contact HP Support to determine compatibility before updating their software. IMPORTANT: Some systems shipped from the factory with version 6.1.0.
Other supported software Software Supported versions Linux X9000 clients • Red Hat Enterprise Linux 5.2, 5.3, 5.4, 5.5, 5.6, 5.7 (all 64 bit) nl • SUSE Linux Enterprise Server 11 (64 bit) • SUSE Linux Enterprise Server 10 SP3 (64 bit) • openSUSE 11.1 (64 bit) • CentOS 5.2, 5.3, 5.4, 5.5, 5.6, 5.
Enhancements This section provides information about enhancements added to a release. Enhancements in the 6.1.3 release The 6.1.3 release provides the option, -l, for placing log files in an alternative location for the ibrix_fsck -p 1 and ibrix_fsck -p 2 commands. Use the -l option to prevent the root file system from running out of space. For example: ibrix_fsck -p 1 -l /home/user/ ibrix_fsck -p 2 -l /home/user/ In these examples, /home/user/ is the alternative location. Enhancements in the 6.1.
• ◦ Monitoring CIFS services on file serving nodes. This is done with the new ibrix_cifsmonitor command. ◦ Share-level permissions for users or groups. You can assign share-level permissions on the GUI or with the ibrix_cifsperms command. Data validation enhancements: ◦ New data retention, utilization, and validation reports. ◦ New autocommit feature. Files that are not changed during the Autocommit period automatically become WORM or WORM-retained when the period expires.
ibrix_fs_tune -c -d -f FSNAME • Remote replication now supports replicating from a 5.x cluster to a 6.1.x cluster, or from a 6.1.x cluster to a 5.x cluster. Although 6.1 to 5.x replication is supported, HP recommends that the target version not be lower than the source version when replicating. The following table lists the supported replications. IBRIX OS version on source IBRIX OS version on target 6.1.x 6.1.x 6.1.x 5.6.x 5.6.x 6.1.x 6.0 6.
restrictions have been implemented on rename operations. The following restrictions apply to hybrid file systems: • Only directories created in version 6.0 or later can become snap tree roots. • If the old directory is not in a snap tree and the new directory is in a snap tree, rename is allowed only if the object being renamed is snapable (that is, it has the new inode format). The following restrictions apply to both hybrid file systems and pure 6.x file systems: • A snap tree root cannot be renamed.
original file is deleted post replication, the directory quota accounted for it gets decremented. Since the newly created file was not marked with the directory quota ID, it was never accounted for. As a result, a reduction in quota usage was shown post replication. The fix was to mark the replica created with the quota ID same as that of the original file, so any data written into this file is accounted for against the set quota ID.
Fixes in the 6.1.2 release • Resolution for a critical potential security issue. Refer to the Security Bulletin available at: https://h20566.www2.hp.com/portal/site/hpsc/public/kb/docDisplay/? docId=emr_na-c03510876 • The CIFS shadow copy feature that was disabled in the 6.1.1 release has been renabled by default in the 6.1.2 release. For more information about the feature, see the HP IBRIX X9000 Network Storage System File System User Guide.
• When a file system containing a CIFS share was replicated in continuous mode, file deletions from the CIFS share were not propagated to the target. • The NIC monitor failed with a segmentation fault. • The HP IBRIX X9000 Network Storage System File System User Guide did not explain that when a quotas file is imported, the quotas are stored in a different, internal format. When a quotas file is exported, it contains lines using the internal format.
CIFS • CIFS and X9000 Windows clients cannot be used together because of incompatible AD user to UID mapping. You can use either CIFS or X9000 Windows clients, but not both at the same time on the cluster. • The X9000 CIFS server does not support connections from Linux SMB clients. The workaround is to use NFS for Linux. • Alternate Data Streams (ADS) are not supported.
1. Disable the SMB2 protocol on all nodes: ibrix_cifsconfig -t -S SupportSmb2=0 2. Restart the CIFS service on all nodes: ibrix_server -s -t cifs -c restart You may also need to restart the Windows client, as the original negotiated protocol, SMB2, might be cached by the client. Restarting the client renegotiates the protocol back to SMB1. • Be sure to remove Active Directory users from the X9000 share admin list before removing them from Active Directory.
Block snapshots • Snapshot creation may fail while mounting the snapshot. The snapshot will be created successfully, but it will not be mounted. Use the following command to mount the snapshot manually: ibrix_mount -f -m / • Quotas are disabled on block level snapshots (for example, MSA2000 snapshots) and the quota information from the origin file system is not carried to the block level snap file system. Block level snapshots are temporary file systems that are not writable.
Data retention and validation • The ibrix_reten_adm command fails if the date string specified with -e contains spaces. As a workaround, use the following command to enter date strings containing spaces: /usr/local/ibrix/sbin/ibr_reten_adm -e expire_time -f FSNAME -P PATHLIST • The ibrix_vs_snap command cannot delete a block snapshot file system that is enabled for data retention. Instead, use the ibrix_fs command with the -R option.
2. Run the following command to exclude all files in the .webdav directory: # ibrix_avconfig -a -E -f FS1 -P /FS1/.webdav/ -x '*' 3. Reset the immutable bit on the .webdav directory: # chattr +i .webdav/ 4. Exclude all files in the .DAV directory for each HTTP/WebDAV share created: # ibrix_avconfig -a -E -f FS1 -P /FS1/httpshare/.DAV/ -x '*' Segment evacuation • The segment evacuator cannot evacuate segments in a READONLY, BROKEN, or UNAVAILABLE state.
components to toggle from Up, to Stale, and back to Up. Common causes of failures in the monitoring system include: ◦ Reboot of a file-serving node ◦ Network connectivity issues between the management console and a file serving node ◦ Resource exhaustion on a file serving node (CPU, RAM, I/O or network bandwidth) While network connectivity and resource exhaustion issues should be investigated, they can occur normally due to heavy workloads.
service snmpd restart • On X9320/X9720 systems, the virtual SAS manager and VC connect manager must be configured manually for HP Support. • On HP SIM 7.1, X9320/X9300 nodes are discovered as “HP X9320 NetStor FSN” if MSA storage is registered on the cluster nodes. This does not affect sending alerts to HP Support.
Documentation changes and additions File system support for 32-bit and 64-bit mode The section “Creating a file system” on page 12 in the HP IBRIX X9000 Network Storage System File System User Guide contains out-of-date information about 64-bit mode and 32-bit mode. In the 6.1.1 and later releases, file systems are created in 64-bit mode by default. See “Implementation changes in the 6.1.1 release” (page 6) for more information.
Antivirus support information The 6.1 documentation is missing the following information about the quarantine utility: • The “Configuring Antivirus support” section in the 6.1 version of the HP IBRIX X9000 File System User Guide does not contain the following text: “All infected files are quarantined by default. Use the quarantine utility (ibrix_avquarantine) to manage the quarantined infected files, such as to move, delete, list or reset the infected files.
Upgrades The upgrade procedure is provided in the administrator guide for your storage system. Contact HP Support for assistance with the procedure. Compatibility/Interoperability Note the following: • Every member of the cluster must be running the same version of IBRIX OS software. • The cluster must include an even number of file serving nodes. • All X9000 clients must be running 6.0 or later. Documentation feedback HP is committed to providing documentation that meets your needs.
