From: Theodore Tso <tytso@mit.edu>
To: "Richard Höchenberger" <richard@r-selected.de>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Severe data corruption with ext4
Date: Mon, 23 Mar 2009 11:08:04 -0400 [thread overview]
Message-ID: <20090323150804.GG13368@mit.edu> (raw)
In-Reply-To: <b2080d80903230720m16af65c4t992b9cc34c44b914@mail.gmail.com>
On Mon, Mar 23, 2009 at 03:20:03PM +0100, Richard Höchenberger wrote:
> Hi Ted, I just compiled and installed 2.6.29-rc8 vanilla. Before
> running it, I booted from a live CD and fsck'd all my file systems to
> get them into a consistent, clean state.
>
> Now, after booting 2.6.29-rc8 and writing stuff to dm-14 (/usr), I again get:
>
> ----------
> Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
> block=135274289954816, b_blocknr=0
> Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
> Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
> Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
> block=135274289954816, b_blocknr=0
> Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
> Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
> Mar 23 15:01:02 bakunin kernel: grow_buffers: requested out-of-range
> block 135274289954816 for device dm-14
> Mar 23 15:01:02 bakunin kernel: EXT4-fs error (device dm-14):
> ext4_xattr_delete_inode: inode 4501: block 135274289954816 read error
> ----------
Hmm, so the block number is: 7B0800000000 that indicats that
i_file_acl is 0, but the bits in i_file_acl_high are set. E2fsck
doesn't currently detect and fix this case --- which is a bug in
e2fsck that I'll fix --- but it begs the question how the
i_file_acl_high could have gotten set in the first place.
Was this a freshly created ext4 filesystem, or one that was converted
from ext3?
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Theodore Tso <tytso@mit.edu>
To: "Richard Höchenberger" <richard@r-selected.de>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Severe data corruption with ext4
Date: Mon, 23 Mar 2009 11:08:04 -0400 [thread overview]
Message-ID: <20090323150804.GG13368@mit.edu> (raw)
In-Reply-To: <b2080d80903230720m16af65c4t992b9cc34c44b914@mail.gmail.com>
On Mon, Mar 23, 2009 at 03:20:03PM +0100, Richard Höchenberger wrote:
> Hi Ted, I just compiled and installed 2.6.29-rc8 vanilla. Before
> running it, I booted from a live CD and fsck'd all my file systems to
> get them into a consistent, clean state.
>
> Now, after booting 2.6.29-rc8 and writing stuff to dm-14 (/usr), I again get:
>
> ----------
> Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
> block=135274289954816, b_blocknr=0
> Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
> Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
> Mar 23 15:01:02 bakunin kernel: __find_get_block_slow() failed.
> block=135274289954816, b_blocknr=0
> Mar 23 15:01:02 bakunin kernel: b_state=0x00310021, b_size=4096
> Mar 23 15:01:02 bakunin kernel: device blocksize: 4096
> Mar 23 15:01:02 bakunin kernel: grow_buffers: requested out-of-range
> block 135274289954816 for device dm-14
> Mar 23 15:01:02 bakunin kernel: EXT4-fs error (device dm-14):
> ext4_xattr_delete_inode: inode 4501: block 135274289954816 read error
> ----------
Hmm, so the block number is: 7B0800000000 that indicats that
i_file_acl is 0, but the bits in i_file_acl_high are set. E2fsck
doesn't currently detect and fix this case --- which is a bug in
e2fsck that I'll fix --- but it begs the question how the
i_file_acl_high could have gotten set in the first place.
Was this a freshly created ext4 filesystem, or one that was converted
from ext3?
- Ted
next prev parent reply other threads:[~2009-03-23 15:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 9:44 Severe data corruption with ext4 Richard
2009-03-20 10:01 ` Andrew Morton
2009-03-22 13:26 ` Richard
2009-03-23 2:05 ` Theodore Tso
2009-03-23 9:10 ` Richard
2009-03-23 12:17 ` Theodore Tso
2009-03-23 12:17 ` Theodore Tso
2009-03-23 14:20 ` Richard Höchenberger
2009-03-23 15:08 ` Theodore Tso [this message]
2009-03-23 15:08 ` Theodore Tso
2009-03-23 15:12 ` Richard Höchenberger
2009-03-26 18:05 ` Richard Höchenberger
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=20090323150804.GG13368@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@r-selected.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.