From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux ext4 Development <linux-ext4@vger.kernel.org>
Subject: Fwd: ext4_check_descriptors: Block bitmap for group 0 overlaps block group descriptors
Date: Sun, 11 Jun 2023 09:27:45 +0700 [thread overview]
Message-ID: <17d7e7f8-ad8d-1696-32b7-3ff9fd4548c1@gmail.com> (raw)
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Hi,
>
> Fail to mount a filesystem in kernel 6.4.0
>
> The Filesystem is clean. fsck -fp reports no errors
>
> # uname -a
> Linux medusa.dds.de 6.4.0-rc5 #2 SMP PREEMPT_DYNAMIC Wed Jun 7 08:11:59 CEST 2023 x86_64 GNU/Linux
> # mount /dev/bigvg/lv_dat /mnt
> mount: /mnt: mount(2) system call failed: Structure needs cleaning.
> dmesg(1) may have more information after failed mount system call.
>
> Under Kernel 6.3.4 everything works with this Filesystem
The reporter then pasted short dmesg snippet:
> [ 104.501659] EXT4-fs (dm-9): ext4_check_descriptors: Block bitmap for group 0 overlaps block group descriptors
> [ 104.501664] EXT4-fs (dm-9): group descriptors corrupted!
>
See Bugzilla for the full thread and attached dumpe2fs, lspci, and systeminfo.
Anyway, I'm adding it to regzbot:
#regzbot introduced: v6.3..v6.4 https://bugzilla.kernel.org/show_bug.cgi?id=217534
#regzbot title: Block bitmap for group 0 overlaps block group descriptors, causing mount failure
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217534
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-06-11 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 2:27 Bagas Sanjaya [this message]
2023-06-14 12:11 ` Linux regression tracking #update (Thorsten Leemhuis)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17d7e7f8-ad8d-1696-32b7-3ff9fd4548c1@gmail.com \
--to=bagasdotme@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®