This section describes how the filer reacts to a disk failure when a hot spare disk is available.
If a disk fails, the filer continues to run without losing any data but has a somewhat degraded performance.
Caution: Replace the disk as soon as possible, because a second disk failure could cause the filer to lose the entire file system.
The filer logs a warning message in the /etc/messages file on the root volume every hour after a disk fails.
To ensure that you notice the failure, the filer automatically shuts itself off in 24 hours, by default, or in a period you set with the raid.timeout option to the options command. You can restart the filer without fixing the disk, but it continues to shut itself off periodically until you repair the problem.
Caution: Check the /etc/messages file on the root volume once a day for important messages. You can automate checking this file with a script on a remote host that periodically searches the file and then alerts you.
After you replace a disk, the filer detects the new disk when the system boots. The filer starts file service and reconstructs the missing data in the background with minimum interruption to service.
Copyright © 1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02334
File: trbl9.htm
Last updated: 04/26/99 08:11:58