test

Sun Cluster 2.2 System Administration Guide

Maintaining the /var File System

Because Solaris and Sun Cluster software error messages are written to the /var/adm/messages file, the /var file system can become full. If the /var file system becomes full while the node is running, the node will continue to run, but you probably will not be able to log into the node with the full /var file system. If the node goes down, Sun Cluster will not start and a login will not be possible. If this happens, you must reboot in single-user mode (boot -s).

If the node reports a full /var file system and continues to run Sun Cluster services, follow the steps outlined in the following procedure.

How to Repair a Full /var File System

In this example, phys-hahost1 has a full /var file system.

  1. Perform a switchover.

    Move all logical hosts off the node experiencing the problem.


    phys-hahost2# haswitch phys-hahost2 hahost1 hahost2

  2. Remove the node from the cluster membership.

    If you have an active login to phys-hahost1, enter the following:


    phys-hahost1# scadmin stopnode

    If you do not have an active login to phys-hahost1, halt the node.

  3. Reboot the node in single-user mode.


    (0) ok boot -s
INIT: SINGLE USER MODE

Type Ctrl-d to proceed with normal startup,
(or give root password for system maintenance): root_password
Entering System Maintenance Mode

Sun Microsystems Inc. SunOS 5.6 Generic August 1997

  4. Perform the steps you would normally take to clear the full file system.

  5. After the file system is cleared, enter multiuser mode. 


    # exit

  6. Use the scadmin startnode command to cause the node to rejoin the configuration.


    # scadmin startnode