No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The N8300 reports error while creating the file system

Publication Date:  2012-12-12 Views:  124 Downloads:  0

Issue Description

There is a set of N8300 in the user’s site, while it is building the file system, it implements very slowly, it takes more than 10 minutes, there will report the error however the file system has built successfully, it doesn’t take any influence sooner after deleting it. The error information is as the following picture:

Alarm Information

The device reports error: “the file system hasn’t been mounted in the node”.

Handling Process

1. Check the device’s heartbreak connection.
2. Restart the subsidiary node.

Root Cause

1. Login each node via the account “support” and the password “symantec”, and execute the command “df -h” one by one and check the mounting status in each node, the outcome is printed as followed:
N8300_01:~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             108G   11G   92G  11% /
udev                  7.9G  296K  7.9G   1% /dev
/dev/sda5              93G  7.0G   81G   8% /opt
/dev/sda6              18G  469M   16G   3% /var
/dev/sda7              18G  367M   16G   3% /tmp
tmpfs                 4.0K     0  4.0K   0% /dev/vx
                      2.0T   17G  2.0T   1% /vx/CMS_website
                      100G  392M   94G   1% /vx/ftp_doc_sas
                      1.0T  4.6G 1012G   1% /vx/CMS_insite
                      2.0T   11G  2.0T   1% /vx/NFS_fs_sata
                      100M  3.3M   91M   4% /var/lib/nfs/sm
                      500G   69G  405G  15% /vx/ftp_dmp_sas
                      2.0T   14G  2.0T   1% /vx/CMS_zhizuo
                      200G  517M  188G   1% /vx/ftp_fs_sata
                      300G  151G  141G  52% /vx/CIFS_fs_sata
  N8300_02:~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             108G   11G   92G  11% /
udev                  7.9G  292K  7.9G   1% /dev
/dev/sda5              93G  6.3G   82G   8% /opt
/dev/sda6              18G  694M   16G   5% /var
/dev/sda7              18G  239M   16G   2% /tmp
tmpfs                 4.0K     0  4.0K   0% /dev/vx

From the above information, we can see there hasn’t mounted the file system created in the N8000 file system on the slave node, we conclude the error is caused by the subsidiary node can’t mount the file system.
2. Export the “var/log/messages” and “/var/VRTSvcs/log/engine_A.log” logs of the subsidiary node, check the “” log, we find the device has lots of split-brain error.
2012/03/15 10:30:45 VCS ERROR V-16-10031-1005 (N8300_02) CVMCluster:???:monitor:node - state: out of cluster
reason: network split-brain detected
Hence, we conclude the controller B is abnormal is caused by the split-brain.