From: Johannes Berg <johannes@sipsolutions.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 wrote extents on ext2 fs?
Date: Sat, 10 Jan 2015 00:38:35 +0100 [thread overview]
Message-ID: <1420846715.9731.1.camel@sipsolutions.net> (raw)
In-Reply-To: <20150109233009.GB31554@thunk.org>
On Fri, 2015-01-09 at 18:30 -0500, Theodore Ts'o wrote:
> What I suspect happened is that some kind of garbage --- perhaps
> simply a single 4k block of 0xFF's --- got written into the inode
> table. This would trigger this sort of complaint from e2fsck.
Ok, makes sense. It's a USB flash drive, so perhaps it just messed up
with its FTL and showed a deleted block in place of the real one.
> > Perhaps this is just a consequence of check ordering though - maybe if
> > the inode flags get corrupted then the EXTENTS flag is just the first
> > one that will be tested in the e2fsck code?
>
> Yes, this is one of the first things that e2fsck 1.42.x would test
> for.
Thanks for the confirmation.
Thanks,
johannes
prev parent reply other threads:[~2015-01-09 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 22:18 ext4 wrote extents on ext2 fs? Johannes Berg
2015-01-09 23:30 ` Theodore Ts'o
2015-01-09 23:38 ` Johannes Berg [this message]
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=1420846715.9731.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).