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 X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 31A82C43613 for ; Fri, 21 Jun 2019 19:34:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ED3D2208CA for ; Fri, 21 Jun 2019 19:34:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726092AbfFUTei convert rfc822-to-8bit (ORCPT ); Fri, 21 Jun 2019 15:34:38 -0400 Received: from mail.wl.linuxfoundation.org ([198.145.29.98]:47604 "EHLO mail.wl.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725992AbfFUTei (ORCPT ); Fri, 21 Jun 2019 15:34:38 -0400 Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id C1F8228AC6 for ; Fri, 21 Jun 2019 19:34:37 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id B4DE928BA0; Fri, 21 Jun 2019 19:34:37 +0000 (UTC) From: bugzilla-daemon@bugzilla.kernel.org To: linux-ext4@vger.kernel.org Subject: [Bug 203943] ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails Date: Fri, 21 Jun 2019 19:34:36 +0000 X-Bugzilla-Reason: None X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: AssignedTo fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Product: File System X-Bugzilla-Component: ext4 X-Bugzilla-Version: 2.5 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: yann@ormanns.net X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: fs_ext4@kernel-bugs.osdl.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT X-Bugzilla-URL: https://bugzilla.kernel.org/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org https://bugzilla.kernel.org/show_bug.cgi?id=203943 --- Comment #5 from Yann Ormanns (yann@ormanns.net) --- Thank you for your support, Ted. About one week before the RAID got degraded, I created a full file-based backup, so at least I can expect minimal data loss - I just would like to save the time it would take to copy ~22TB back :-) Before filing a possible bug in the correct section for RAID, I'd like to comprehend the steps you described. In fact e2fsck does not report inode numbers, only variables ("%$i", and so does it for blocks, "%$b"). Using the the total inode count number in debugfs leads to an error: share ~ # tune2fs -l /dev/mapper/share | grep "Inode count" Inode count: 366268416 share ~ # debugfs /dev/mapper/share debugfs 1.44.5 (15-Dec-2018) debugfs: stat 366268416 366268416: File not found by ext2_lookup Or did I get you wrong? -- You are receiving this mail because: You are watching the assignee of the bug.