From: Borislav Petkov <bp@alien8.de>
To: Ritesh Harjani <ritesh.list@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Vaibhav Jain <vaibhav@linux.ibm.com>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: EXT4-fs error (device sda5) in ext4_update_backup_sb:165: Filesystem failed CRC
Date: Thu, 26 May 2022 17:42:34 +0200 [thread overview]
Message-ID: <Yo+f6ml4jB1jxjfw@zn.tnic> (raw)
In-Reply-To: <20220526145402.slc4ve5vrlewyutm@riteshh-domain>
On Thu, May 26, 2022 at 08:24:02PM +0530, Ritesh Harjani wrote:
> Could you please help us understand little more about your setup. Is
> this (sda5) somehow a backup image saved/restored using e2image?
Nah, just a separate, normal partition.
> So, recently I have also been reported with a similar problem, where in filesystem
> image which was saved using e2image on v5.17 kernel (with e2fsck 1.45.5 (07-Jan-2020)).
> Then on upgrading the kernel to v5.18, when this FS image (via e2image) was mounted
> using loop device (or restored to a block device), the above error messages
> were observed.
That could be the case. See, this box is simply a test laptop where I
boot kernels all the time and userspace doesn't get updated, pretty
much. So if old tools massage the superblock and new kernels then touch
it again, that could mean there's some discrepancy there... but what do
I know - I have not clue about fs.
In any case, 5.18-rc7+ didn't have those earlier messages but simply:
EXT4-fs (sda5): warning: mounting fs with errors, running e2fsck is recommended
EXT4-fs (sda5): mounted filesystem with ordered data mode. Quota mode: disabled.
but I haven't run any fsck yet. Since this is a test box, it doesn't
matter a whole lot, though.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2022-05-26 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 12:55 EXT4-fs error (device sda5) in ext4_update_backup_sb:165: Filesystem failed CRC Borislav Petkov
2022-05-26 14:54 ` Ritesh Harjani
2022-05-26 15:42 ` Borislav Petkov [this message]
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=Yo+f6ml4jB1jxjfw@zn.tnic \
--to=bp@alien8.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=vaibhav@linux.ibm.com \
/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