From: Baokun Li Kernel commit 0a6ce20c1564 ("ext4: verify orphan file size is not too big") limits the maximum supported orphan file size to 8 << 20. However, in e2fsprogs, the orphan file size is set to 32–512 filesystem blocks when creating a filesystem. With 64k block size, formatting an ext4 fs >32G gives an orphan file bigger than the kernel allows, so mount prints an error and fails: EXT4-fs (vdb): orphan file too big: 8650752 EXT4-fs (vdb): mount failed Therefore, synchronize the kernel change to e2fsprogs to avoid creating orphan files larger than the kernel limit. Signed-off-by: Baokun Li --- v1->v2: * Revert the changes in ext2fs_default_orphan_file_blocks() v1: https://lore.kernel.org/r/20251112122157.1990595-1-libaokun@huaweicloud.com lib/ext2fs/orphan.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/lib/ext2fs/orphan.c b/lib/ext2fs/orphan.c index 14ac3569..6124a59a 100644 --- a/lib/ext2fs/orphan.c +++ b/lib/ext2fs/orphan.c @@ -164,6 +164,12 @@ errcode_t ext2fs_create_orphan_file(ext2_filsys fs, blk_t num_blocks) memset(zerobuf, 0, fs->blocksize); ob_tail = ext2fs_orphan_block_tail(fs, buf); ob_tail->ob_magic = ext2fs_cpu_to_le32(EXT4_ORPHAN_BLOCK_MAGIC); + /* + * Kernel commit 0a6ce20c1564 ("ext4: verify orphan file size is not + * too big") limits the maximum supported orphan file size to 8 << 20. + */ + if (num_blocks * fs->blocksize > (8 << 20)) + num_blocks = (8 << 20) / fs->blocksize; oi.num_blocks = num_blocks; oi.alloc_blocks = 0; oi.last_blk = 0; -- 2.46.1