[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANubcdWP9CC0HZQrbyqBomiy2opkBP1gLhnj6n9-m4sKDOyeig@mail.gmail.com>
Date: Mon, 28 Aug 2023 12:44:54 +0800
From: Stephen Zhang <starzhangzsd@...il.com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: adilger.kernel@...ger.ca, yi.zhang@...wei.com, djwong@...nel.org,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
zhangshida@...inos.cn, stable@...nel.org,
Andreas Dilger <adilger@...ger.ca>
Subject: Re: [PATCH v4] ext4: Fix rec_len verify error
Theodore Ts'o <tytso@....edu> 于2023年8月5日周六 20:20写道:
>
>
> On Thu, 03 Aug 2023 14:09:38 +0800, zhangshida wrote:
> > With the configuration PAGE_SIZE 64k and filesystem blocksize 64k,
> > a problem occurred when more than 13 million files were directly created
> > under a directory:
> >
> > EXT4-fs error (device xx): ext4_dx_csum_set:492: inode #xxxx: comm xxxxx: dir seems corrupt? Run e2fsck -D.
> > EXT4-fs error (device xx): ext4_dx_csum_verify:463: inode #xxxx: comm xxxxx: dir seems corrupt? Run e2fsck -D.
> > EXT4-fs error (device xx): dx_probe:856: inode #xxxx: block 8188: comm xxxxx: Directory index failed checksum
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] ext4: Fix rec_len verify error
> (no commit info)
Hi Ted,
It appears that you might have missed this one in the recent git tree.
The presence of "(no commit info)" may indicate some apply failures.
Best regards,
Shida
>
> Best regards,
> --
> Theodore Ts'o <tytso@....edu>
Powered by blists - more mailing lists