From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Report of data corruption on ext4
Date: Fri, 24 Jul 2009 10:24:17 -0500 [thread overview]
Message-ID: <4A69D221.3000609@redhat.com> (raw)
FYI:
Bug 513221 - ext4 filesystem corruption and data loss
https://bugzilla.redhat.com/show_bug.cgi?id=513221
is a bit troubling.
Unfortunately it has a lot of false-starts in the bug comments so it
looks a little convoluted and hard to follow.
But the upshot is, he seems to swaths of null bytes in his mail files,
on 4k boundaries, not correlated with extent boundaries necessarily.
And he's not had crashes or power losses, he says.
Not a lot to go on yet, but something to keep an eye on.
-Eric
reply other threads:[~2009-07-24 15:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A69D221.3000609@redhat.com \
--to=sandeen@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).