Installation guide

– A disk or ﬁle system is corrupt

If a disk or ﬁle system is corrupt, run the fsck command on the ﬁle

system. The fsck command checks and repairs UNIX File Systems

(UFS). If fsck ﬁnds something wrong, it prompts you for an action

to take. Use extreme care under these circumstances so that you do

not inadvertently overwrite or remove any ﬁles. Refer to the fsck

(8)

reference page for more information. If you have an Advanced File

System (AdvFS), disk corruption is very unlikely.

AdvFS provides disk recovery during the mount procedure that

corrects the disk structures. You do not need to run the fsck

command or any other command. Consequently, recovery of AdvFS

is very rapid.

3.9 Shutting Down the System

The following sections describe the shutdown procedures and the recovery

strategies that you use in both controlled and unexpected shutdowns. The

ﬁrst part discusses procedures for handling controlled shutdowns. The

second part discusses guidelines and recommendations for handling and

recovering from unexpected shutdowns.

_______________________ Note _______________________

You can also use the SysMan dxshutdown command for some of

these tasks.

There are several good reasons to stop the system in a controlled

shutdown. For example:

• You need to upgrade your software or add new hardware to your

conﬁguration. You shut down the system to set up the new additions,

make the necessary adjustments to your conﬁguration ﬁles, and build a

new kernel.

• You have been monitoring the hardware error log and have noticed

repeated warnings. You suspect that your hardware may soon fail so

you shut down the system and examine the problem.

• You notice that system performance is degrading rapidly. You check the

system statistics and conclude that some changes to the system would

improve performance. You shut down and tune the system.

• You notice signs of possible ﬁle system corruption. You shut down the

system and run the fsck program to ﬁx problems or to conﬁrm that

none exist.

3–16 Starting Up and Shutting Down the System