HP StorageWorks Scalable File Share - Manual (Page 40)

Operating the system 3–8
If a service shows the
unload-failed
state, reboot the server to force the file system to unload. (For
information on file system service states, see Table 4-3 on page 4-7.)
If a server is booted while the file system is in the
stopped
or
not-stopped
state, the MDS and OST
services that normally run on that server will not start.
3.8 Starting a file system
If a file system is stopped, or some of its services are in the
stopped
state, you can start the file system and
make it ready for use by entering the
start filesystem filesystem_name
command, as shown in
the following example. In this example, the
scratch
file system is started:
CAUTION: When the
start filesystem
command is run, it checks whether there are file system
devices that need to be formatted; if it finds any such devices, it displays a message to allow you to
decider whether to format the devices.
If MDS or OST devices are formatted unnecessarily, data will be lost. Before you decide whether to format
any devices when starting a file system, please read the information in Section 3.8.1.
sfs> start filesystem scratch
Command id 47
15:20:24 south2 --
15:20:27 south2 --
15:20:27 south2 --
15:20:27 south3 --
15:20:27 south4 --
15:20:27 south2 -- Configuring the OSTs
15:20:28 south4 --
15:20:29 south3 --
15:20:29 south3 -- Enabling the OST service ost37
15:20:29 south4 -- Enabling the OST service ost38
15:20:38 south4 -- Enable ost38: service started on south4
15:20:43 south3 -- Enable ost37: service started on south3
15:20:48 south3 --
15:20:48 south4 --
15:20:53 south2 --
15:20:53 south2 -- Enabling the MDS service mds9
15:20:53 south1 --
15:20:53 south1 -- Creating clumanager MDS symlinks for scratch
15:20:53 south2 -- Configuring the MDS
15:20:53 south2 -- Waiting for configMds and configAdm commands (48 51) to finish
15:20:58 south2 -- Enable mds9: service started on south2
15:21:03 south2 --
15:21:03 south2 --
Command has finished:
south2 --
*** Server States *** Completed: south[1-4]
To verify that the file system has started, enter the command shown in the following example:
sfs> show filesystem
Name State Services
------------- -------------- ----------------------------------
scratch started mds9: recovering, ost[37-38]: running
(See Table 4-3 on page 4-7 for a description of file system service states.)
Immediately after the file system is started, the MDS and OST services may be in the
starting
state. The
state later changes to
recovering
and later again to
running
. Alternatively, the state may skip the
starting
and
recovering
states and go directly to the
running
state.