Table of Contents

NAME

halt - stop the filer

SYNOPSIS

halt [ -d ] [ -t mins ] [ -f ]

DESCRIPTION

halt flushes all cached data to disk, turns off the non-volatile RAM, and drops into the monitor. Any time you power-off the filer, you should first execute the halt command to conserve the batteries on the non-volatile RAM.

NFS clients can maintain use of a file over a halt or reboot (although experiencing a failure to respond during that time), but CIFS clients cannot do so safely. Therefore, if the filer is running CIFS, the halt command invokes cifs terminate, which requires the -t option. If the filer has CIFS clients and you invoke halt without -t, it displays the number of CIFS users and the number of open CIFS files. Then it prompts you for the number of minutes to delay. cifs terminate automatically notifies all CIFS clients that a CIFS shut-down is scheduled in mins minutes, and asks them to close their open files. CIFS files that are still open at the time the filer halts will lose writes that had been cached but not written.

halt logs a message in /etc/messages to indicate that the filer was halted on purpose.

OPTION

-d
Dumps system core before halting.
-t mins
Halts after the indicated number of minutes, or after all CIFS files that were open have been closed, whichever is sooner.
-f
Applies only to filers in a cluster. If you enter the halt -f command on a filer, its partner does not take over.

CLUSTER CONSIDERATIONS

After you enter the halt command on a filer in a cluster, the other filer in the cluster automatically takes over the filer that you halted. If you do not want takeover to happen, use the halt -f command.

The halt command is not available in partner mode. That is, you cannot enter the partner halt command on the live filer after it takes over the failed partner. This is because a filer that has been taken over is no longer running and cannot be halted.

SEE ALSO

na_cifs_terminate(1), na_partner(1), na_reboot(1), na_savecore(1), na_messages(5)

Table of Contents