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>


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


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

Publication Date:  2012-07-19 Views:  282 Downloads:  0
Issue Description

Product and version information:

  • S5500T V100R001 V100R002
  • S5600T V100R001 V100R002
  • S5800T V100R001 V100R002
  • S6800T V100R001 V100R002
  • Application server operating system: Kylin Linux 3

1.The host and the storage array were properly connected.
2.Log in to the storage array management system and map a LUN to the host.
3.An ext2 file system created on the mapped LUN was successfully mounted.
4.When a file was being copied to the mounted target directory, the host broke down immediately.

Alarm Information
Handling Process

1.Power off the host and power it on again. Wait for the system to start normally.
2.Run the mkfs.ext3 /dev/sdX or mkfs -t ext3 /dev/sdX command to create a file system. #sdX indicates a drive letter identified by the operating system.
3.Run the mount /dev/sdX /mnt command to mount the file system.

Root Cause
This was a Kylin ext2 file system issue. Kylin confirmed that any security factor added to an ext2 file system may lead to a host breakdown.
1.Kylin engineers recommend that ext3 file systems or other file systems be used to replace ext2 file systems on Kylin Linux 3 operating systems due to the breakdown issue on ext2 file systems.
2.If ext2 file systems are absolutely necessary, contact Kylin service engineers for assistance.