HP StorageWorks Scalable File Share - Manual (Page 39)

Stopping a file system 3–7
3.7 Stopping a file system
When you create a file system using the
create filesystem
command, the file system is started and
ready for use. You can stop a file system by entering the
stop filesystem filesystem_name
command.
The
stop filesystem filesystem_name
command stops the file system and at the same time
preserves user connections. When you stop a file system, any active I/O operations are suspended. The
application that was performing the I/O operation is blocked until the file system is next restarted and the
client node has reconnected. While the file system is stopped, any new access (mount, unmount, I/O
operation) is blocked until the file system is next restarted and the client node has reconnected.
While the file system is stopped, a client that attempts a new mount operation is blocked until the file system
is next restarted and until all existing clients have reconnected. If one or more clients fail to reconnect
immediately, the file system waits for up to ten minutes before accepting new mount requests.
In the following example, the
scratch
file system is stopped:
sfs> stop filesystem scratch
Command id 42
15:11:31 south2 --
15:11:34 south2 --
15:11:34 south2 --
15:11:34 south3 --
15:11:34 south4 --
15:11:35 south2 -- Disabling the MDS service mds9
15:11:35 south3 --
15:11:35 south3 -- Disabling the OST services for ost37
15:11:36 south4 --
15:11:36 south4 -- Disabling the OST services for ost38
15:11:45 south2 -- Disable mds9: service stopped on south2
15:11:45 south3 -- Disable ost37: service stopped on south3
15:11:50 south2 --
15:11:50 south3 --
15:11:55 south2 --
15:11:55 south4 -- Disable ost38: service stopped on south4
15:11:55 south4 --
15:11:55 south2 -- Filesystem (scratch) stopped successfully
Command has finished:
south2 --
*** Server States *** Completed: south[2-4]
To verify the status of the file system, enter the command shown in the following example:
sfs> show filesystem
Name State Services
------------- -------------- ----------------------------------
scratch stopped mds9: stopped, ost[37-38]: stopped
If the file system is not in the
stopped
state, or if any of the MDS or OST services belonging to the file
system are not in the
stopped
state, an error has occurred. See Section 5.5 for information on how to
determine the source of any errors.
Normally, at the time that you enter the command to stop a file system, all of the MDS and OST services
belonging to a file system are in the
running
(or
recovering
) state and all servers are running. However,
if an MDS or OST service is not running or some of the servers are down when you want to stop the file
system, you can still use the
stop filesystem
command. The command fails on any servers that are
down, but continues to work on the remaining servers. If the command fails to complete on one or more
servers, the state of the file system will be
not-stopped
. If you reboot these servers, the services will not
start and the state of the file system will then be
stopped
.