When you perform the mount operation for file systems, like the ext4 file system in instances associated with local volumes (for example, instances of the Big data type and Local SSD type) for the first time, lock contention may occur. This can cause command hangs.

Causes

The inode table needs to be initialized when the mount operation is performed for the first time. For Linux kernel versions 2.6.37 and later, the lazyinit (delayed initialization) feature is enabled by default. This causes the initialization of the inode table to be postponed until after the mount operation. During initialization, the local volume consumes significant throughput. As a result, the business operates less stably, and operational exceptions may also occur, such as lagging or slow response.

Solutions

Method 1: Disable lazyinit during mkfs formatting

Execute the following command to disable lazyinit.

mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 /dev/sda1

View the I/O status of the formatted local volume.

iostat -x 5

When the I/O activity of the local volume shows zero, which indicates that initialization is completed, perform the mount operation.

Method 2: Use xfs file system or select an image with kernel version 4.x or later

Using the xfs file system can effectively avoid this issue. Or, select images such as veLinux 1.0 CentOS compatible edition with 5.10 kernel, CentOS Stream 9, and other images with kernel version 4.x or later. This can also mitigate this issue.

Last updated: 2026.04.13 16:50:03

Public security network record in Beijing: No. 11010802032137