From: Theodore Ts'o <tytso@mit.edu>
To: "gnehzuil.liu" <gnehzuil.liu@gmail.com>
Cc: Dave Jones <davej@redhat.com>, Borislav Petkov <bp@alien8.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: EXT4 corruption on Linus latest tree.
Date: Wed, 27 Feb 2013 13:03:02 -0500 [thread overview]
Message-ID: <20130227180302.GB16966@thunk.org> (raw)
In-Reply-To: <3F9FDA73-A142-43FB-BFF2-35C200355736@gmail.com>
On Thu, Feb 28, 2013 at 01:07:10AM +0800, gnehzuil.liu wrote:
>
> Thanks for the report. From the result, I think extent status tree
> is root cause because of wrong logical-to-physical block mapping. I
> am very sorry about that. I will try to fix the bug ASAP.
Here's a hint as to what's going on:
% bc
bc 1.06.95
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
obase=16
# This is the block number printed in the error message
152052301
910224D
# This is the block number reported by debugfs
688923213
2910224D
It looks like something in the code is masking off the low 25 bits, so
we're losing the higher bits from the physical block number. That
should be pretty easy to find and fix....
- Ted
prev parent reply other threads:[~2013-02-27 18:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 15:43 EXT4 corruption on Linus latest tree Dave Jones
2013-02-27 15:55 ` Borislav Petkov
2013-02-27 16:04 ` Dave Jones
2013-02-27 16:32 ` Theodore Ts'o
2013-02-27 16:44 ` Theodore Ts'o
2013-02-27 16:56 ` Dave Jones
2013-02-27 17:07 ` gnehzuil.liu
2013-02-27 18:03 ` Theodore Ts'o [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=20130227180302.GB16966@thunk.org \
--to=tytso@mit.edu \
--cc=bp@alien8.de \
--cc=davej@redhat.com \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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