Document Type | Troubleshooting
Category | Installation
Applicable Product Version | 7FS02PS
Document Number | TINTS003
Issue
When registering a CM Cluster, a cluster start failed issue may occur where the cluster does not start due to an error in specifying the cfile path.
- For CM Cluster operation, during the cluster registration process, cluster files (cfile) are specified, and multiple files can be registered separated by โ,โ or specified with โ*โ in the file path.
- When registering cfile in a TAS environment, if โ+โ is prefixed to the path, it is recognized as a TAS-specific path. If the โ+โ is omitted in the cfile path in TAS environment, the cluster will not start properly.
When โ+โ is omitted in the cfile path
For example, when disk space is planned to be configured as /dev/tas/disk01, /dev/tas/disk02, /dev/tas/disk03, a '*' file is created under /dev/tas and the cluster start fails.
Step | Example Command |
|---|---|
Start CM | tbcm -b |
Register network | cmrctl add network --name [ public network name] --nettype public --ifname [interface name] cmrctl add network --name [ private network name] --nettype private --ipaddr 192.168.x.x --portno [port number] |
Register cluster | cmrctl add cluster --name [cluster name] --pubnet [public network name] --incnet [private network name] --cfile "/dev/tas/*" |
Start cluster | [root@tac2 ~]# cmrctl start cluster --name cls Failed to start the resource 'cls' |
Log recorded when cm start fails
2025/04/25 14:07:40.483 [1] cm_actio:8961(04) [cls] Cluster `cls` init start 2025/04/25 14:07:40.483 [1] cm_fd.c :0133(04) [cls] [ERROR] Cannot open [/dev/tas/*:Invalid argument] 2025/04/25 14:07:40.483 [1] cm_file.:1621(04) [cls] [ERROR] Cannot open CM cluster file (/dev/tas/*) 2025/04/25 14:07:40.483 [1] cm_file.:1643(04) [cls] [ERROR] Failed to open CM files (0/1) 2025/04/25 14:07:40.483 [1] cm_actio:9186(04) [cls] [ERROR] Failed to init CM files 2025/04/25 14:07:40.483 [1] cm_actio:7682(04) [cls] all cluster resource down 2025/04/25 14:07:40.483 [1] cm_actio:9475(04) [cls] Cluster 'cls' down
Check /dev/tas path
[root@tac2 ~]# cd /dev/tas [root@tac2 tas]# ll total 0 -rw-r--r-- 1 root root 0 Apr 25 14:07 '*' lrwxrwxrwx 1 root root 6 Apr 25 14:04 disk01 -> ../sdb lrwxrwxrwx 1 root root 6 Apr 25 14:04 disk02 -> ../sdc lrwxrwxrwx 1 root root 6 Apr 25 14:04 disk03 -> ../sdd
Cause
This issue occurs due to an error in specifying the cfile path when registering the CM Cluster. In a TAS environment, prefixing the path with โ+โ when registering cfile causes it to be recognized as a TAS-specific path.
Solutions
This can be resolved by correctly setting the /dev/tas path and re-registering the cluster.
Step | Example Command |
|---|---|
Delete cluster | cmrctl del cluster --name [cluster name] |
Register cluster | cmrctl add cluster --name cls --pubnet pub2 --incnet int2 --cfile "+/dev/tas/*" |
Start cluster | cmrctl start cluster --name [cluster name] MSG SENDING SUCCESS! |