From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205197] kernel BUG at fs/ext4/extents_status.c:884
Date: Fri, 15 Mar 2024 12:14:32 +0000 [thread overview]
Message-ID: <bug-205197-13602-BV4AeT3Ahn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205197-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205197
--- Comment #7 from Antony Amburose (antony.ambrose@in.bosch.com) ---
Thank you for the response. I understand now , why there was not much attention
to this issue. Sorry for providing a minimal information in the first
communication...
We have back-ported the interesting changes from upstream (~70 of them) and
could still see the problem. I have reported the issue based on old kernel to
have the continuity. The old issue reported as well seen while mounting an
encrypted sd card and we have also seen this on an encrypted volume, but its
onboard storage. I thought it is logical to continue the discussion here as you
had given some debugging hints and issue did not progress as the old reporter
could not reproduce the problem but we could even after backporting the change.
I will create the bug based on the latest kernel in future. Thanks for the
hint.
The issue could be reproduced in a sequence where we interrupt the power. From
our decade long experience working with ext4, we have never seen an issue where
we could corrupt the ext4 volume in a way that it is not mountable by
executing a power loss sequence. That was main reason to report the issue to
the community experts. Ofcourse we have some paid support and also inhouse
kernel engineers, and I thought it is also better to report to the community
experts as the old bug is still open and we have a reliable reproduction .My
current assumption is either that we have a problem with our sequence or
problem with handling encrypted ext4 partition.
Regarding our knowhow and usage of tooling , we can work with the hex dump and
understand the ext4 disk layout and also work with the e2fsprogs to debug the
problem. Hence, we expect only some debugging hints and direction and hopefully
we try to solve the issues together.
As the device resets cyclically , we could not hook into the device and get the
/dev/sdXX . The existing tooling only get the encrypted data .We will try to
resolve this situation and somehow get the hex dump and provide more details on
the nature of corruption and will also provide the fsck output.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-03-15 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 12:38 [Bug 205197] New: kernel BUG at fs/ext4/extents_status.c:884 bugzilla-daemon
2019-10-15 13:53 ` [Bug 205197] " bugzilla-daemon
2019-10-17 6:50 ` bugzilla-daemon
2019-10-23 13:13 ` bugzilla-daemon
2019-10-24 6:58 ` bugzilla-daemon
2024-03-04 4:17 ` bugzilla-daemon
2024-03-14 21:31 ` bugzilla-daemon
2024-03-15 12:14 ` bugzilla-daemon [this message]
2024-03-15 17:03 ` bugzilla-daemon
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=bug-205197-13602-BV4AeT3Ahn@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.