RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1071909 - mkfs.ext4: Lazy_itable_init is not enabled by default when ext4 module is not loaded
Summary: mkfs.ext4: Lazy_itable_init is not enabled by default when ext4 module is not...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: e2fsprogs
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Lukáš Czerner
QA Contact: Eryu Guan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-03 12:50 UTC by Lukáš Czerner
Modified: 2014-06-18 08:27 UTC (History)
3 users (show)

Fixed In Version: e2fsprogs-1.42.9-4.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:07:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Lukáš Czerner 2014-03-03 12:50:15 UTC 
Description of problem:

Lazy inode table initialization sbould be enable d by default, however the check whether the kernel implementation support lazy itable initialization requires ext4 module to be loaded. So in the case that ext4 is not loaded mkfs.ext4 will not enable lazy inode table initialization by default.

How reproducible:
always


Steps to Reproduce:
1.modprobe -r ext4
2.mkfs.ext4 /dev/sda
3.

Actual results:
Inode table will be initialized at mkfs time making it tun much longer than it should.


Expected results:
Inode table initialization will be skipped and will be done lazily after the file system is mounted.
Comment 6 Eryu Guan 2014-03-12 10:18:37 UTC 
Verified with e2fsprogs-1.42.9-4.el7

remove ext4 module and do mkfs, with e2fsprogs-1.42.9-4.el7 the mkfs is much faster and I can see ext4lazyinit kernel thread after mounting the partition

[root@ibm-x3550m3-06 ~]# time mkfs -t ext4 /dev/mapper/testvg-lv50g
mke2fs 1.42.9 (28-Dec-2013)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
3276800 inodes, 13107200 blocks
655360 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2162163712
400 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done


real    0m1.661s
user    0m0.146s
sys     0m0.150s
[root@ibm-x3550m3-06 ~]# mount /dev/mapper/testvg-lv50g /mnt/ext4
[root@ibm-x3550m3-06 ~]# ps -ef | grep lazy
root     26481     2  0 18:15 ?        00:00:00 [ext4lazyinit]

With e2fsprogs-1.42.9-3.el7 mkfs is slower and there's no ext4lazyinit kernel thread.

Set to VERIFIED.
Comment 7 Ludek Smid 2014-06-13 11:07:24 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.