Manual Pages
Table of Contents
na_halt - stop the filer
halt [ -t <mins> ] [ -f ]
halt [ -d <dump_string> ]
halt shuts down the filer. The halt command has two
forms. The first form flushes all data to disk, and performs
a clean shutdown. The second form dumps system core
without flushing cached data.
NFS clients can maintain use of a file over a halt or
reboot, although the filer will fail to respond during
that time. CIFS, FCP, and iSCSI clients cannot safely
maintain use of a file over a halt or reboot. If the
filer is running CIFS, FCP or iSCSI, you may use the -t
option to specify the time before shutdown. If halt is
invoked without -t, it displays the number of CIFS users,
the number of open CIFS files, the number of mapped LUNs
and the number of connected FCP and iSCSI clients. 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. FCP and iSCSI will not notify
clients, but will allow administrators to confirm that the
mapped LUNs are not in use. LUNs that are in use at the
time the filer halts will result in client failures.
halt logs a message in /etc/messages to indicate that the
filer was halted on purpose.
-t mins Initiates a clean system shutdown after the
indicated number of minutes. Applies only if
the filer is running CIFS, FCP or iSCSI.
-
-f
- Applies only to filers in a cluster. If you
enter the halt -f command on a filer, its partner
does not take over.
-
-d dump_string
-
Dumps system core and halts the filer. This
results in a dirty shutdown; cached data will
not be flushed to disk. The dump_string should
indicate the reason for the core dump. Because
it results in a dirty shutdown, the -d option
generally should not be used for normal maintenance
(see NOTES below).
After you enter the halt command on a filer in a cluster,
the other filer in the cluster automatically takes over
the halted filer. 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.
To shut down the filer for maintenance, use the first form
of halt, since it does a clean shutdown. That is, halt [
-t <mins> ] [ -f ].
When the -d option is used, cached data is not flushed to
disk. All data not yet on disk is stored in the NVRAM.
The filer will automatically replay NVRAM during the next
boot, bringing the disks up to date with the most recent
operation. However, if NVRAM loses charge, some of the
most recently modified data may be lost. Because of this,
the -d option should be used only to produce coredumps
requested by technical support. NVRAM retains charge for
three days, so all data will be intact if NVRAM is
replayed within three days of the dirty shutdown.
na_cifs_terminate(1), na_partner(1), na_reboot(1),
na_savecore(1), na_messages(5)
Table of Contents