IBRIX Fusion 3.1 Release Notes

Transcription

1 Release Date April 2009 Version IBRIX Fusion Version 3.1 Release 46 Compatibility New Features Version 3.1 CLI Changes RHEL 5 Update 3 is supported for Segment Servers and IBRIX Clients RHEL 5 Update 2 is supported for Segment Servers and IBRIX Clients RHEL 4 Update 6 is supported for IBRIX Clients RHEL 4 Update 7 is supported for IBRIX Clients SLES 10 SP2 is supported for IBRIX Clients None Table 1 summarizes differences in command behavior in the Version 3.1 user interface. Table 1 CLI Changes for IBRIX Fusion V3.1 Command ibrix_activedirectory ibrix_fm -t -I addr ibrix_fmha -m [-y] ibrix_fs ibrix_host ibrix_mount ibrix_recover ibrix_replicate V3.1 Changes Dropped UID and GID arguments, which are no longer needed to configure Active Directory. New functionality to assign a cluster network address to the Fusion Manager. Added confirmation option to migrate Fusion Manager HA without prompting for user information. Introduces -N option on file system migrations to skip host health checks during the migration process. The default is to include the health check. Introduces -o maxsegs option when creating 32-bit file systems to specify a maximum number of segments. Introduces -N option on file system migrations to skip host health checks during the migration process. The default is to include the health check. Added root_ro parameter to limit the root user to readonly access on export-controlled Fusion Clients in a hostgroup. Run twice for full recovery: once to recover configuration, and again to recover the database. Added -X option to force the reuse of bad volume groups and logical volumes even if the Segment Server that owns the bad segment is unavailable. 1

2 2 New usage for ibrix_mount Fixes included in Release 46 Fixes included in Release 45 Fixes included in Release 38 When mounting a file system where Export Control is enabled, Fusion Clients must be granted specific read-only or read-write access rights to the file system. In addition, the root user can be restricted to read-only access on export-controlled systems in a hostgroup by adding the root_ro parameter to the ibrix_mount command. The syntax is: ibrix_mount -f FSNAME -o {RW RO} [root_ro] -g GROUPLIST -m MOUNTPOINT This example mounts file system ifs1 on the clients in hostgroup finance at mountpoint /ifs, granting read-write access to the clients but limiting the root user to read-only access: ibrix_mount -f ifs1 -o RW root_ro -g finance -m /ifs1 Bug The IBRIX health check utility now verifies that the appropriate mountpoint exists on the backup server before failover is initiated. Explicit message text has been added for situations where the mountpoint is missing. Bug Improved the amount of time required to create a large number of quotas. Bug 10731/ Improved failover completion time when quotas are enabled. Bug For IBRIX Windows client, we added support for the creation of hard links. Bug Corrected possible deadlock during segment migration under heavy I/O load. Bug Fixed a rare instance where directory cache attributes did not get updated after a rename from an NFS client. Bug Improved handling for a mix of mapped and non-mapped remote write operations to the same file. Bug Rename request for a file in a directory at the same time as a lookup request for that same directory no longer causes a block of all nfsd threads until the timeout is reached. Bug RPC timeout no longer causes rename operation failure during heavy server load. Bug Fixed conditions within IBRIX Fusion to decrease the possibility of triggering a Linux rename bug that results in a deadlock. Bug Fixed a deadlock condition on the server releasing ownership of a segment during fail back. Bug Implemented support for remote directory change notification for Windows Clients. Bug Added validation code to prevent the creation of root as an IBRIX mountpoint. Bug Unmount operations for client host groups now work when the mount point is specified, but not the filesystem name. Bug Extraneous ide_rename_verify log messages have been removed. Bug The IBRIX file system creates case sensitive file names and does case sensitive lookups on the Segment Server, i.e. Hello.txt and hello.txt are different files. If you ask for file HELLO.txt, it will not be found. Windows applications assume that these files are the same so IBRIX has implemented logic in the IBRIX Windows Client to ensure that searches for such files are done using case insensitive algorithms. In this release, the IBRIX Windows Client s handling of file names with regard to case has been modified as follows: By default the IBRIX Windows Client will down case file names when creating files and when searching for files. This parameter setting is CaseInsensitive=Yes. If you know that all of the directories and files that your Windows applications will access will be created from the IBRIX Windows Client, or if you know that all of your files are created

3 3 with lower case names, this new default will provide the best performance. You will always find your files no matter what case you specify when accessing the files through the IBRIX Windows Client. If you do not want this down casing to occur then set the following registry key value: HKLM\SOFTWARE\Ibrix\IDE\IDEFS\CaseInsensitive (REG_SZ): No If you have conflicting file names (multiple files with the same name but different cases, such as the Hello.txt examples above), then please note the following: If you attempt to open a file with the incorrect case, your CaseInsensitive setting will determine the behavior: NEW DEFAULT MODE: CaseInsensitive=Yes a. Your "missed" filename is lower cased. If this file exists, you get this file. b. If the lower cased file does not exist, it will either be created (if you specified this) or you will get a file not found error. This opens the possibility of creating a lowercased version of the file when the intention was to open or edit another file. OLD DEFAULT MODE: CaseInsensitive=No a. Your "missed" filename will match the first entry in the directory that is found using a case insensitive match. If there are more than one version of this file that match the pattern, you will be given the first file encountered in the cache or directory entry. This may or may not be the intended file. If you use the correct case, you will always get the intended file. Bug A possible deadlock involving the transfer of quota information from one user to another was fixed. Bug The ibrix_quota command now uses the -v verbose option as a default. It does not have to be specified on the ibrix_quota command. Bug The -h option of the chown command is now supported. Please refer to the man page for chown for further information. Bug UTF-8 character encoding is now the default for data read from or written to the IBRIX file system by IBRIX Windows Clients.The character encoding used is controlled by the registry entry HKLM\SOFTWARE\Ibrix\IDE\IDEFS\CodePage. The new default is The default in previous releases of the IBRIX Windows Client was Bug An issue with the management of the IBRIX Windows Client cache has been resolved. The issue could result in failed opens and missing files when enumerating large directories. Bug The default number of server threads running on IBRIX Segment Servers has been increased from 10 to 16. Bug A Segment Server crash when running the ibrix_rebalance command has been resolved. The crash was most likely to occur if massive deletes were being done against the file system while the rebalancer was running. Bug IBRIX uses watermark values to manage available space on segments. There are 3 watermarks: 1. Create Watermark - When available segment space is at or below this amount, new file system objects will not be created on the segment. Existing files on the segment may continue to be appended to. 2. Spillover Watermark - When available segment space is at or below this amount, new file system objects used to extend large files that spill over from other segments will not be created on the segment. Existing files on the segment may continue to be appended to.

4 4 3. Write Watermark - When available segment space is at or below this amount, no more data can be written to the segment, i.e. appends will not be allowed on the segment. The default watermark settings have changed and they are as follows: Create Watermark - lesser of 10% of segment space or 50 GB Spillover Watermark - lesser of 11% of segment space or 55 GB Write Watermark - lesser of 1% of segment space or 5 GB You should not need to adjust these watermarks in normal situations. Please contact IBRIX Customer Support if you require assistance. Please add more space or reclaim space when your segments reach 90% full to ensure smooth operation of your file system. Bug The ibrix_health command has been adjusted to treat UUID mismatches as a warning in the health report instead of a failure. UUID checks can fail if an IBRIX server is deleted from the configuration and then re-added. Bug The following options have been added to the ibrix_fmha command: ibrix_fmha -c displays the Fusion Manager HA configuration ibrix_fmha -M migrates to the standby Fusion Manager and powers off the Fusion Manager that was migrated away from ibrix_fmha -P {on off} powers on or powers off the other Fusion Manager HA node Bug The ibrix_health command has been adjusted to ignore segments that have been marked bad by the system administrator. Bug Automatic backups of the Fusion Manager data base are now enabled by default after installing the Fusion Manager. Bug The ibrix_recover command had an erroneous check that required Fusion Manager backups to be on, in order for the recovery to run. This check has been removed. Bug The ibrix_host command has been enhanced to allow a server to be failed over even if the server s IPMI interface cannot be accessed, such as in the event of a power failure. Add the -X flag to the ibrix_host command to force the failover in this case. Restrictions / Limitations NFS Locking Support. NFS locking is not supported when using RHEL5.2 or 5.3 on the Segment Servers. LVM Snapshots Only Are Supported. Although the FusionSnap feature is documented to provide both CX-based and LVM2-based snapshots, V3.1 supports LVM2 only. The maximum number of segments owned by a single server that can be snapped is 29. Fusion Manager HA 3.0 Reinstallation Requirement. Users of IBRIX Fusion 3.0 who installed Fusion Manager HA, when upgrading to V3.1, must reinstall Fusion Manager HA after the upgrade. The format of the configuration file changed for V3.1. In order to use the new configuration file, those users must rerun install_fmha after upgrading. This requirement does not apply to users of IBRIX Fusion V2.2 who upgrade to V3.1. RHEL5 U1 and U2 Performance Tuning For customers with Linux RHEL5 U1 or RHEL5 U2 Segment Servers, improved performance with the default CFQ disk scheduler can be achieved by tuning the scheduler to run with slice_idle = 0. The default of slice_idle=8 will cause a degradation of NFS single threaded reads. Bug Client directory policy cannot be unset with ibrix_fs_tune -U. If a client (or client group) is set to use a directory policy by running the ibrix_fs_tune -R command, the policy cannot be reset to none with ibrix_fs_tune -U. For the change to take effect, the client service must be restarted.

5 5 Bug Fusion Manager GUI does not display new file systems correctly. If a user creates one or more file systems under the Configuration > File Systems tab, the File Systems pane on the right lists the new file systems, but they are not listed in the left navigation bar under the File Systems folder. In order to list the new file systems in the navigation pane, the user must close the GUI and reopen it. Bug Client tuning parameter cannot be reset with ibrix_host_tune -U -n. If you change the tuning parameter for a client (or client group) back to its default values using ibrix_host_tune U n, client services must be restarted for the change to take effect. To work around this issue, manually set the client tuning to the default value instead of trying to reset it. Bug Restarting ibrix_server on S1 causes remote mirrors on S2 to degrade. After an ibrix_server restart, all remote mirrors must be rebuilt to clear up all degraded remote mirrors. Run ibrix_mirror -r -A from the Fusion Manager to do this. Bug Delay in propagating replication policy settings throughout cluster. If you change the replication policy on a host with ibrix_replicate, allow a short interval (typically 30 seconds) for the hosts to synchronize with the Fusion Manager. Bug If a Segment Server is failed over while an ibrix_rebalance job is running, the job must be stopped and restarted. If you do not restart the ibrix_rebalance job, it may continue to run but it will not make any progress. Bug: Backup utility s configuration may be deleted after migration or failover. Verify that the backup utility s configuration file (/etc/ibrix/monitor.xml) is valid after a Fusion Manager HA migration or failover. In some circumstances, the file is deleted and a default file regenerated. In the default file, backups are turned off (backup.on is set to false), and the location where IBRIX Fusion writes its backups (backup.path) reverts to /var/lib/ibrix/backup. Bugs 8331 and 9061 both apply to use of Fusion Manager HA on a system with an ILO power source controller. Bug During FM-HA installation, do not accept the default user name and password (ibrix/ibrix) as presented by the FM-HA installation script. Use your ILO user name and password instead. Installation will not succeed with the IBRIX user credentials. This is not an issue for IPMI power source users. Bug Do not configure ILO to automatically power on servers when they are shut down. This setting interferes with the STONITH process. During failover, the node assuming control believes it has shut down its partner, but the ILO setting prevents it. In this situation, it is necessary to power down the node through its ILO console by cold boot or a system reset. Bug In order to ensure that failover does not occur during the Fusion Manager HA upgrade procedure, suspend Fusion Manager HA operation before upgrading Fusion Manager on either node by putting the program into administrative mode. New versions of IBRIX Fusion often introduce changes and additions to the configuration database. In order to make sure these changes are incorporated into your installation, we recommend you reinstall Fusion Manager HA while in administrative mode as shown in this procedure. Bug If using Fusion Manager HA, only one FM-HA pair can be installed per routable subnet regardless of the number of clusters within that subnet. This is a restriction that can be traced back to the multicasting method used by the Linux-HA heartbeat service and there is no workaround.

6 6 Bug When installing Fusion Manager HA, do not use uppercase letters in host names. Bug When using Fusion Manager HA, if you have to manually start the Fusion Manager, do not use /etc/init.d/ibrix_fusionmanager start. Use $IBRIXHOME/fm-ha/ocf-fusionmanager start instead. Licensing Refer to your end-user license agreement for supported features and terms of use by IBRIX, Inc. 300 Concord Road Billerica, MA All Rights Reserved.