From: Richard <richard@r-selected.de>
To: linux-ext4@vger.kernel.org
Subject: Re: Severe data corruption with ext4
Date: Sun, 22 Mar 2009 14:26:34 +0100 [thread overview]
Message-ID: <b2080d80903220626s5fffdbf3i907cb4b215670ce6@mail.gmail.com> (raw)
In-Reply-To: <20090320030121.1fa8e6d3.akpm@linux-foundation.org>
Hello again,
now on the same system (hardware configuration unchanged, except that
I attached a DVD burner yesterday), I got dozens of errors like these:
----------
Mar 22 13:47:33 bakunin kernel: __find_get_block_slow() failed.
block=197478301302784, b_blocknr=0
Mar 22 13:47:33 bakunin kernel: b_state=0x00188021, b_size=4096
Mar 22 13:47:33 bakunin kernel: device blocksize: 4096
Mar 22 13:47:33 bakunin kernel: __find_get_block_slow() failed.
block=197478301302784, b_blocknr=0
Mar 22 13:47:33 bakunin kernel: b_state=0x00188021, b_size=4096
Mar 22 13:47:33 bakunin kernel: device blocksize: 4096
Mar 22 13:47:33 bakunin kernel: grow_buffers: requested out-of-range
block 197478301302784 for device dm-14
Mar 22 13:47:33 bakunin kernel: EXT4-fs error (device dm-14):
ext4_xattr_delete_inode: inode 1022: block 197478301302784 read error
----------
Please not that I had run an fsck on the mentioned device only a
couple hours earlier, with no errors found.
Now, does this indicate a hardware problem?
My drives' SMART info reports not a single reallocated sector. But one
drive has a high Hardware_ECC_Recovered count, but I got it that's
nothing to actually worry about. Well, it might indicate bad cabling,
though.
Richard
next prev parent reply other threads:[~2009-03-22 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2080d80903200244u7fbcc150g6724a84c9b3b2054@mail.gmail.com>
2009-03-20 10:01 ` Severe data corruption with ext4 Andrew Morton
2009-03-22 13:26 ` Richard [this message]
2009-03-23 2:05 ` Theodore Tso
2009-03-23 9:10 ` Richard
2009-03-23 12:17 ` Theodore Tso
2009-03-23 14:20 ` Richard Höchenberger
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=b2080d80903220626s5fffdbf3i907cb4b215670ce6@mail.gmail.com \
--to=richard@r-selected.de \
--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).