lazy_journal_init – If enabled, the journal inode will not be fully zeroed out by mke2fs. If the option value is omitted, it defaults to 1 to enable lazy inode table zeroing. This speeds up filesystem initialization noticeably, but it requires the kernel to finish initializing the filesystem in the background when the filesystem is first mounted. lazy_itable_init – If enabled and the uninit_bg feature is enabled, the inode table will not be fully initialized by mke2fs.There is an option to enable or disable this feature while running mkfs.ext4 command: This only affects if you have just created an ext4 filesystem. As a result, your RAID rebuild is going to operate at minimal speed. A process called “ext4lazyinit” runs in the background to create rest of all inode tables. This feature allows the faster creatation of a file system. When creating an ext4 file system, the Linux kernel uses lazy initialization. A note about lazy initialization and ext4 file system The recovery speed was around 4000K/sec and will complete in approximately in 22 hours. Next, I type the command cat /proc/mdstat and it reported that md0 is active and recovery is in progress. Recently, I build a small NAS server running Linux for one my client with 5 x 2TB disks in RAID 6 configuration for all in one backup server for Linux, Mac OS X, and Windows XP/Vista/7/10 client computers. Why speed up Linux software RAID rebuilding and re-syncing?
0 Comments
Leave a Reply. |