Problem Information
Item | Description |
Storage type | Distributed storage |
Product version | FusionStorage 8.0.0; FusionStorage 8.0.1 |
Problem type | Capacity expansion |
Keyword | Storage pools; node expansion; Capacity expansion failures |
Problem Symptom
A node that has been added to a storage pool or has been removed from a storage pool fails to be expanded. Error message: The system has an internal error. The configuration file already exists on the node to be expanded.
Problem Diagnosis
Check logs of the FSM node.
zgrep -ai "check node failed. error code" /var/log/oam/fsm/manager/run/storageService.log
Check the configuration file of the agent on the faulty node. If osd_x_x_para= exists, for example, x.x.x.x in the following figure.
Log in to the node to be added.
cat /opt/fusionstorage/agent/conf/agentMonitor |grep -i osd
Causes
Possible causes are as follows: The configuration file on the node to be added is not completely cleared. The node becomes faulty or the network is abnormal when the node is being removing from a storage pool.
Solution
Run the following command on the FSM node to clear the configuration file.
sh /opt/dsware/client/bin/dswareTool.sh --op clearNode -type osd -ip x.x.x.x -poolId all
2. Re-expand the capacity after command execution.
Check After Recovery
Check the configuration file of the agent on the faulty node. If osd_x_x_para= exists, for example, x.x.x.x in the figure in Problem Symptom.
Log in to the node to be added.
cat /opt/fusionstorage/agent/conf/agentMonitor |grep -i osd
3. Re-expand the capacity after command execution.Suggestion and Summary
If a node or network fault occurs during the node removing process, the configuration file of the node may not be cleaned completely. Therefore, you need to manually clean the file before adding the node to a storage pool.
Applicable Versions
All
