HP StorageWorks Scalable File Share - Manual (Page 247)

Troubleshooting file systems 9–23
9.26.4 Troubleshooting the stop filesystem command
If the
stop filesystem
command fails, attempt to correct the problem as follows:
1. Identify the servers where the command failed; they may have been down when the command was
run. If this is the case, reboot the servers.
2. Enter the
stop filesystem
command again.
If the command fails again, continue with the remaining steps.
3. On the MDS server (or on the administration server if the MDS server is down), unload the MDS
software by entering the following command:
# cluadmin -- service disable mdsN
where
mdsN
is the MDS service for the file system (for example,
mds2
).
4. Ensure that the MDS software has unloaded, as follows:
a.
Search for a directory that has the name of the MDS service; for example, if the MDS service is
called
mds2
, check that the following directory does not exist:
/proc/fs/lustre/mds/mds2
If the directory in question exists, reboot the server.
b. Enter the
lsmod
command to verify that the Lustre kernel modules have been unloaded from the
MDS server. If only one file system is being served, the following modules will no longer be
loaded on the MDS server:
•
mds
•
lov
•
osc
•
mdc
•
obdclass
•
lvfs
•
lnet
If only one file system is being served, and one or more of the above modules still exists on the
server (indicating that the Lustre modules have not been unloaded cleanly), reboot the server.
5. On each Object Storage Server, unload the OST services as follows. You must perform these steps on
each Object Storage Server that has OST services serving the file system.
a.
Enter the command shown in the following example. You must enter the command once for each
individual OST service (for example, if there are two OST services on an Object Storage Server,
you must enter the command twice on that server—once for each OST service):
# cluadmin -- service disable ostN
where
ostN
is the OST service for the file system (for example,
ost4
).
b. Ensure that the OST software has unloaded on the Object Storage Server, as follows:
i.
Search for a directory that has the name of an OST service; for example, if the OST service
is called
ost4
, check that the following directory does not exist:
/proc/fs/lustre/obdfilter/ost4
If the directory in question exists, reboot the Object Storage Server.
ii. Enter the
lsmod
command to verify that the Lustre kernel modules have been unloaded
from the server. If only one file system is being served, the following modules will no longer
be loaded on the Object Storage Server:
•
mds
•
lov
•
osc