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 [thread overview]
Message-ID: <bug-203943-13602-EqKWhqvEWE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203943-13602@https.bugzilla.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.
next prev parent reply other threads:[~2019-06-21 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 6:51 [Bug 203943] New: ext4 corruption after RAID6 degraded; e2fsck skips block checks and fails bugzilla-daemon
2019-06-21 7:15 ` [Bug 203943] " bugzilla-daemon
2019-06-21 12:40 ` bugzilla-daemon
2019-06-21 14:52 ` bugzilla-daemon
2019-06-21 18:29 ` bugzilla-daemon
2019-06-21 19:34 ` bugzilla-daemon [this message]
2019-06-21 20:47 ` bugzilla-daemon
2019-06-22 7:48 ` bugzilla-daemon
2019-06-22 8:06 ` bugzilla-daemon
2025-10-31 1:33 ` 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-203943-13602-EqKWhqvEWE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox