HP IBRIX X9000 Series 5.5.
© Copyright 2012 Hewlett-Packard Development Company, L.P.
Version: 5.5.5 (build 5.5.314) Description This release contains updates to HP X9000 File Serving Software, HP X9320 and X9720 Network Storage Systems, and HP X9300 Network Storage Gateway systems. The X9000 Software features a highly scalable file system, CIFS, NFS, FTP, and HTTP file services, high availability, remote replication, data tiering, and CLI and GUI management interfaces, and is installed on HP Network Storage System and Network Storage Gateway servers.
Other supported software Software Supported versions Linux X9000 clients • Red Hat Enterprise Linux 5.1, 5.2, 5.3, 5.4, 5.5 (all 64 bit) nl • Red Hat Enterprise Linux 4 Updates 5, 6, 7, 8 (all 64 bit) • SUSE Linux Enterprise Server 11 (64 bit) • SUSE Linux Enterprise Server 10 SP3 (64 bit) • openSUSE 11.1 (64 bit) • CentOS 4.5, 5.1, 5.2, 5.3, 5.
◦ Linux static user mapping with Active Directory ◦ SMB signing support ◦ Support for consolidating SMB servers with common share names See the user guide and administrator guide for your system for details about the new features. Fixes Corrected in 5.5.5 (build 5.5.314) The following fixes were made in this release: • When a local user or group was deleted, the user or group was not deleted from the CIFS database. • An lwiod failure caused the CIFS service to stop.
• A condition in the CIFS implementation could cause CIFS disconnects and lsassd failures. • When extremely large numbers of files were opened, CIFS users lost access to the CIFS share. • A condition in the CIFS implementation caused a backup application to fail to write a file. • The CIFS implementation failed with lwiod segfault in IbfsSyncLockState(). • When Cygwin was used to create a hard link on a CIFS share, the CIFS implementation did not report that hard links are not supported.
Other operations • A server failed with the error ASSERT[atomic_read(&(*pfs)->ref.ref_counter) != 0] failed: Too many unreferencing. • The fmbackup.zip file could become corrupted. • Old snapshots were not deleted, preventing the snapshot retention policy from working properly. • A race condition caused the system to fail with the error [exception RIP: j_verifyThread+448] - corrupted pJournal->q_verify queue. • A lock condition caused corruption in the management console database.
Corrected in 5.5.257 The following fixes were made in this release: • When a file was uploaded into an FTP share, the file was owned by ftp:ftp, not by the user who uploaded the file. Files uploaded to an FTP share are now owned by the logged-in user. • When a file was uploaded into an HTTP share, the file was owned by daemon:daemon, not by the user who uploaded the file. Files uploaded to an HTTP share are now owned by the user doing the upload.
Failover • An informational message was needed for failback operations requiring the administrator to run the ibrix_pv -a command. • NICs were not failed over in parallel when a server was powered down. Other operations • When a server did not respond because it was rebooting, the error message Err: New inode's required delegation is missing was displayed. • The support ticket feature did not collect the /usr/local/ibrix/log/daily directory. • The Linux SLES10u3 client did not start properly.
IbrixFusionManager- 4. If the RPM is present on the node, remove the RPM: # rpm -e IbrixFusionManager- Migration to an agile management console configuration When a cluster is configured with a dedicated, standard management console, the Quick Restore installation procedure installs both the IbrixFusionManager and the IbrixServer packages on the dedicated, standard management console and on each node of the cluster.
ibrix_exportcfrpreference command can be used to change the network interface preference. • No alert is generated if the continuous remote replication target becomes unavailable. Confirm the connection to the target system by issuing a ping command and by inspecting ibrcfrworker.log. • Sparse files on the source file system are replicated unsparse on the target. That is, all blocks corresponding to the file size are allocated on the target cluster.
• For configurations with two management consoles, if the node hosting the active management console goes down, it is important to reboot it as soon as possible. The management console on that node can then assume a passive role and receive updates from the new active management console. If the node remains down and the node hosting the active management console also goes down, the cluster configuration data may become inconsistent, depending on the order in which the nodes are rebooted.
If a share name contains any of these special characters, the share might not be set up properly on all nodes in the cluster. • Certain special characters do not work in share descriptions.
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.
ibrix_fm_tune -S -o vendorStorageHardwareStaleInterval=1800 The default value of this command is 900; the value is in seconds. A higher value reduces the probably of all components toggling from Up to Stale and back to Up because of the conditions listed above, but will increase the time before an actual component failure is reported. General • On Windows X9000 clients, when Active Directory is switched from the static mapping mode to dynamic mapping, users with Full Control cannot rename files.
Segment evacuation. The following restrictions apply when removing storage from the cluster: • You cannot evacuate or remove the root segment (segment #1). • The file system must be quiescent (no active I/O while a segment is being evacuated). Previous versions of the administrator guide incorrectly stated that the file system can be active. Managing CIFS shares with the Microsoft Management Console (MMC). To manage CIFS shares, open an MMC with the Shared Folders snap-in.
Kernel update 2.6.9-89.35.1.ELsmp is compatible. If the minor kernel update is compatible, install the update with the vendor RPM and reboot the system. The X9000 client software is then automatically updated with the new kernel, and X9000 client services start automatically. Use the ibrix_version -l -C command to verify the kernel version on the client.
Compatibility/Interoperability Note the following: 18 • Every member of the cluster must be running the same version of X9000 Software. • The cluster must include an even number of file serving nodes.
