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.

Knowledge Base

[T Series]Ext2 File System Security Mechanism Led to a Not Responding Host Status

Publication Date:  2012-07-19  |   Views:  465  |   Downloads:  0  |   Author:  q00002810  |   Document ID:  EKB1000008663


Issue Description

Product and version information:

  • S5500T V100R001 V100R002
  • S5600T V100R001 V100R002
  • S5800T V100R001 V100R002
  • S6800T V100R001 V100R002

The storage array was connected to the host and mapped a LUN to the host. An ext2 file system created on the mapped LUN was successfully mounted, but when a file was being copied to the mounted target directory, the host broke down immediately.

Alarm Information


Handling Process

Power off the host and power it on again. After the system is running properly, perform the following operations:
 1. Create a file system.
    The related command is mkfs.ext3 /dev/sdX where sdX indicates the drive letter identified by the operating system.
    You can also create a file system by using the mkfs -t ext3 /dev/sdX command.

 2. Mount the file system.The related command is mount /dev/sdX /mnt.

Root Cause

This was a Kylin ext2 file system issue. Any security factor added to an ext2 file system may lead to a host breakdown.


Kylin engineers recommend that ext3 file systems be used to replace ext2 file systems on Kylin Linux 3 operating systems due to the breakdown issue on ext2 file systems. If ext2 file systems are absolutely necessary, contact Kylin service engineers for assistance.