JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster System Administration Guide     Oracle Solaris Cluster 4.1
search filter icon
search icon

Document Information

Preface

1.  Introduction to Administering Oracle Solaris Cluster

2.  Oracle Solaris Cluster and RBAC

3.  Shutting Down and Booting a Cluster

Overview of Shutting Down and Booting a Cluster

How to Shut Down a Cluster

How to Boot a Cluster

How to Reboot a Cluster

Shutting Down and Booting a Single Node in a Cluster

How to Shut Down a Node

How to Boot a Node

How to Reboot a Node

How to Boot a Node in Noncluster Mode

Repairing a Full /var File System

How to Repair a Full /var File System

4.  Data Replication Approaches

5.  Administering Global Devices, Disk-Path Monitoring, and Cluster File Systems

6.  Administering Quorum

7.  Administering Cluster Interconnects and Public Networks

8.  Adding and Removing a Node

9.  Administering the Cluster

10.  Configuring Control of CPU Usage

11.  Updating Your Software

12.  Backing Up and Restoring a Cluster

A.  Example

Index

Repairing a Full /var File System

Both Oracle Solaris software and Oracle Solaris Cluster software write error messages to the /var/adm/messages file, which over time can fill the /var file system. If a cluster node's /var file system fills up, Oracle Solaris Cluster might not be able to start on that node at the next boot up. Additionally, you might not be able to log in to the node.

How to Repair a Full /var File System

If a node reports a full /var file system and continues to run Oracle Solaris Cluster services, use this procedure to clear the full file system. Refer to Viewing System Messages in Troubleshooting Typical Issues in Oracle Solaris 11.1 for more information.

  1. Assume the root role on the cluster node with the full /var file system.
  2. Clear the full file system.

    For example, delete nonessential files that are contained in the file system.