From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1836C433F5 for ; Thu, 26 May 2022 15:42:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347996AbiEZPmu (ORCPT ); Thu, 26 May 2022 11:42:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236307AbiEZPmt (ORCPT ); Thu, 26 May 2022 11:42:49 -0400 Received: from mail.skyhub.de (mail.skyhub.de [5.9.137.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 12033C8BC2; Thu, 26 May 2022 08:42:44 -0700 (PDT) Received: from zn.tnic (p200300ea97465770329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9746:5770:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 576B61EC0575; Thu, 26 May 2022 17:42:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1653579759; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=zCIU4/CyscCWc5T/l1YpTfxCKoddYSUWbPdUmCDxv9k=; b=d8Rofdbv9ZG0LzGgzXQKCKGMC9eCn79iMgbbTfjwtw5gi9KJfyKrk+pOWXJqNUfZkQuGG8 uAy4tuLk46Jvco+yRjUwxk44Mj9IdL7G/cIf4QbLs9C3sez8fHZ/XaqsD5OiEMgxQGxWNR qSOVS9luVyAk32btQfrtTwtp5CBgk6o= Date: Thu, 26 May 2022 17:42:34 +0200 From: Borislav Petkov To: Ritesh Harjani Cc: linux-ext4 , lkml , Vaibhav Jain , Jan Kara , Theodore Ts'o Subject: Re: EXT4-fs error (device sda5) in ext4_update_backup_sb:165: Filesystem failed CRC Message-ID: References: <20220526145402.slc4ve5vrlewyutm@riteshh-domain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220526145402.slc4ve5vrlewyutm@riteshh-domain> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org 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