HP StorageWorks Scalable File Share - Manual (Page 63)

Viewing file system information 4–7
The MDS and OST service states are described in Table 4-3.
Table 4-2 File system states
State Description
started
All file system services are running. Client nodes will be able to mount the file system and
perform I/O operations.
recovering
All of the services in the file system have been started. However, one or more of the
services are in the
recovering
state—that is, waiting for all previously connected client
nodes to reconnect. When the file system is in this state, all I/O operations in progress on
client nodes will stall. Attempts by client nodes to mount the file system will also stall. After
some time, the file systems will go to the
started
state. (For more information on the
recovery process, see Section 3.8.)
not-started
The file system has been started but one or more of the file system services is not active. It
is normal for the file system to be in the
not-started
state during the time that the
start filesystem filesystem_name
command is executing. When the file
system is in this state, client nodes cannot mount the file system or perform I/O operations
to the file system.
stopped
All of the services in the file system have been stopped. When the file system is in this
state, client nodes cannot mount the file system or perform I/O operations to the file
system. To start the file system, enter the
start filesystem filesystem_name
command.
not-stopped
The file system services are supposed to be stopped (that is, the
stop filesystem
filesystem_name
command has been entered), but one or more of the services are
still active. It is normal for the file system to be in the
not-stopped
state during the time
that the
stop filesystem filesystem_name
command is executing. When the file
system is in this state, client nodes cannot mount the file system or perform I/O operations
to the file system.
needs-restart
The file system services are active. However, a configuration parameter has been
changed, so that the file system configuration data is now out of date. When the file
system is in this state, client nodes may or may not be able to mount the file system and
perform I/O operations to the file system. Stop the file system at your earliest
convenience, and enter the
start filesystem filesystem_name
command.
When you start the file system, the file system configuration is updated before the file
system services restart.
deleting
The
delete filesystem filesystem_name
command has been entered and is
still in progress, or has failed to complete. When the file system is in this state, client
nodes cannot mount the file system or perform I/O operations to the file system.
Table 4-3 File system service states
State Description
down
The server that the file system service was running on has gone to the
down
state.
Because the server is down, the service is not actually running. Normally, the service will
fail over to the backup server so that the
down
state will only be seen for a brief period.
However, if the backup server is not running, the service will stay in the
down
state until
one of the servers in the server pair is rebooted. If the backup server is running, but the
service remains in the
down
state for a long time, enter the
start filesystem
filesystem_name
command to try to start the service again.
load-stalled
The service was starting and is in the process of loading, but has not completed within a
reasonable time. The service may eventually finish loading and go to the
recovering
or
running
state. If so, there is no need to take any action. However, if the service
remains in the
load-stalled
state for 15 minutes, it then moves to the
load-failed
state.
When a service is in the
load-stalled
state, other services are blocked from starting
or stopping on the server.
load-failed
The service has been in the
load-stalled
state for at least 15 minutes. The service will
probably not start. You need to reboot the server to recover from this situation.
When a service is in the
load-failed
state, other services are blocked from starting or
stopping on the server.
recovering
The service is started, but the process of reconnecting all previously connected clients has
not finished.