![使用 `gparted` 扩展分区之后的 `ext4lazyinit`](https://linux22.com/image/1556402/%E4%BD%BF%E7%94%A8%20%60gparted%60%20%E6%89%A9%E5%B1%95%E5%88%86%E5%8C%BA%E4%B9%8B%E5%90%8E%E7%9A%84%20%60ext4lazyinit%60.png)
我刚刚ext4
使用 将常规硬盘上的一个大分区(现在是 2 TiB)扩展到左侧gparted
。花了 5 个小时才完成,但进展顺利。现在,在安装文件系统后,ext4lazyinit
正在后台运行,以 4-6 KiB 的速度在该特定硬盘上写入。它在做什么?互联网说,ext4lazyinit
将某些东西归零。我是否需要担心我的数据?
答案1
Gparted 肯定对新的 ext4 空间进行了更快的“懒惰”格式化,现在挂载时它正在完成工作。这些选项应该mke2fs
可以解释:
lazy_itable_init[= <0 to disable, 1 to enable>]
If enabled and the uninit_bg feature is enabled, the
inode table will not be fully initialized by mke2fs.
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. If the option value is omitted, it
defaults to 1 to enable lazy inode table zeroing.
lazy_journal_init[= <0 to disable, 1 to enable>]
If enabled, the journal inode will not be fully zeroed
out by mke2fs. This speeds up filesystem initialization
noticeably, but carries some small risk if the system
crashes before the journal has been overwritten entirely
one time. If the option value is omitted, it defaults
to 1 to enable lazy journal inode zeroing.