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: Sat, 22 Jun 2019 08:06:09 +0000 [thread overview]
Message-ID: <bug-203943-13602-jz1S1GkxC7@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 #8 from Yann Ormanns (yann@ormanns.net) ---
It seems, as if the data corruption only affects the directories and files,
that the system wrote to while the ext4 FS was not clean.
A quick rsync between my backup fileserver copied nothing of the static data
back to the productive system - so I assume, that these files should be okay
(but of course, I will test that at least randomly).
To sum it up: the data loss affects my backup files locally on this system and
my tv recordings - 934G of total data size are just about right for that.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-06-22 8:06 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
2019-06-21 20:47 ` bugzilla-daemon
2019-06-22 7:48 ` bugzilla-daemon
2019-06-22 8:06 ` bugzilla-daemon [this message]
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-jz1S1GkxC7@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