 | 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:
Changes to the CXFS graphical user interface (GUI):
New login connection choices, including support for a remote shell connection, which connects to the server via a user-specified command shell, such as rsh(1C) or ssh(1). See:“Starting the GUI” in Chapter 4.
The ability for the root user to grant other users permission to execute specific GUI tasks. See:
Use of Java2 for the CXFS GUI, which simplifies the Java installation and co-operation with third-party GUIs. This also enhances the ability to run the GUI through a web browser (via http://server/CXFSManager/). See “Start the GUI” in Chapter 3, and “Install IRIX Software on a CXFS Administration Node” in Chapter 2.
Information about using the right mouse button to access tasks appropriate to the selected GUI item. See Figure 4-2.
Changes to the cxfsd_min and cxfsd_max defaults, and the cxfsd_max legal values; see Table 6-1.
More information about memberships, quorums, and tiebreakers; see Appendix B, “Memberships and Quorums”.
A new figure describing standby mode; see Figure 1-6.
More information about IRIX client-only issues: