This topic describes how to resolve the problem of a metadata server
that is in the "Not running" or "Not added" state.
Context
Use the following steps if, when you run the sfscli lsserver command
on the metadata server, it shows that any of the metadata servers are in either
the "not running" or "not added" state:
Steps
- Start or add the metadata server to the cluster using the appropriate sfscli commands.
- If the previous step does not apply to the situation
or does not solve the problem, complete the following steps:
- Stop all subordinate metadata servers in the cluster
and the master using the stopcluster command.
- On the master metadata server, determine if the Tank.Config and
the Tank.Bootstrap files exist in the /usr/tank/server/config directory.
If they exist, rename them for later use and recreate them by executing the
following commands from the master metadata server.
- Run the Stop Cimom command by entering /usr/tank/admin/bin/stopCimom.
- Make sure no processes are running on the master, and run the setupsfs
-newserver command by entering /usr/tank/admin/bin/setupsfs
-newserver. This command creates a new Tank.Config
file. The results of running the lsserver command
should now indicate that the server is in the "not added subordinate" state.
- Run the sfscli stopserver master_server_name.command.
- Change to the /usr/tank/server/bin directory.
- To find the master disk, run the tank lsdisklabel
-device /dev/rvpathX command. The
disk with a Disk Type of "M" is the master.
- Run the tank extractbootrecord -device /dev/rvpathX command, where /dev/rvpathX is the name of the master metadata
LUN. This command creates a new Tank.Bootstrap
file.
- Run the sfscli startserver master_server_name command.
- Run the sfscli lsserver command.
The server is now the "online master."
- From the master metadata server, start any subordinates
by running the sfscli startserver subordinate_server_name command. At this point, the subordinate server might shutdown. If it does,
it should restart automatically. If it does not restart automatically, start
the server and run the sfscli lsserver command.
The subordinate is now online. If it is not online, run the setupsfs
-newservercommand.
Postrequisites
If there is no Tank.Config file in the /usr/tank/server/config directory
of the subordinate, perform the following steps:
- On the subordinate server, run the setupTank -newserver command.
- On the master metadata server, run the sfscli addserver -port
cluster_port sub_IP_addr command.