 | Note: In this release, relocation is disabled by
default and recovery is supported only when using standby nodes.
A standby node is a metadata server-capable administration node that is configured as a potential metadata server for a given filesystem, but does not currently run any applications that will use that filesystem. To use recovery, you must not run any applications on any of the potential metadata servers for a given filesystem; after the active metadata server has been chosen by the system, you can then run applications that use the filesystem on the active metadata server and client-only nodes. Relocation and recovery are fully implemented, but the number of associated problems prevents full support of these features in the current release. Although data integrity is not compromised, cluster node panics or hangs are likely to occur. Relocation and recovery will be fully supported in a future release when these issues are resolved. |
This update contains the following:
The new rolling annual upgrade policy that permits you to upgrade from 6.5.n to the n+1 or n+4 release, as of 6.5.18f. See “Rolling Upgrades” in Chapter 2.
The time required to update and propagate the database across nodes in the cluster has been significantly decreased.
If you use I/O fencing and ipfilterd (1M) on a node, the ipfilterd configuration must allow communication between the node and the telnet(1) port on the switch. See Appendix B, “IP Filtering Example for the CXFS Private Network”.
The following nodes do not contain system controllers and therefore require I/O fencing for data integrity protection:
Silicon Graphics Fuel visual workstation
Silicon Graphics Octane system
Silicon Graphics Octane2 system
The CXFS Manager graphical user interface (GUI) has added a new icon to represent client-only nodes. See Table 4-3.
In preparation for future CXFS MultiOS client releases, the CXFS software now also allows you to specify the Linux, IBM AIX, and Hewlett-Packard HP-UX operating systems when defining a node; see “Define a Node with the GUI” in Chapter 4, and “Define a Node with cmgr” in Chapter 5. For support details, see the CXFS MultiOS for CXFS Client-Only Nodes: Installation and Configuration Guide and release notes.
This version clarifies the various methods to perform cluster database backups and restorations; see “Cluster Database Backup and Restore” in Chapter 6.
Application programmers should be aware that XFS recently relaxed the requirement that direct I/O be aligned along filesystem block boundaries. As of IRIX 6.5.19f, direct I/O will also be accepted using 512-byte alignment.
This change makes the use of direct I/O on a CXFS partition more consistent with that of other vendor's requirements and thus makes the use of CXFS more transparent. See the description of direct I/O requirements in the fcntl(2) man page.
This version lists the system tunable parameters found in the /var/sysgen/mtune/cell file, some of which should not be modified. See “System Tunable Parameters” in Chapter 6.