From: Theodore Ts'o <tytso@mit.edu>
To: "Nelson, John R" <John_Nelson@student.uml.edu>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Serious bug?
Date: Mon, 30 Jul 2012 22:42:36 -0400 [thread overview]
Message-ID: <20120731024236.GB5027@thunk.org> (raw)
In-Reply-To: <0408C81F72528E40A0D3235A1F67FFC804A61E@SN2PRD0202MB144.namprd02.prod.outlook.com>
On Tue, Jul 31, 2012 at 02:17:03AM +0000, Nelson, John R wrote:
> Hi,
> I created a big 400GB file image and formatted it with mkfs.ext4. the format failed with
>
> Warning: could not erase sector 2: Attempt to write block to filesystem resulted in short write
>
> i then checked my dmesg and found error on my sda3 partition
> [ 119.578077] EXT4-fs error (device sda3): ext4_ext_map_blocks:3769: inode #32243725: comm mkfs.ext4: bad extent address lblock: 53, depth: 2 pblock 0
All of the errors indicate that an extent tree block in inode
#32243725 was corrupted. When you deleted the image file, that
destroyed the evidence, so that's why fsck didn't reveal any problems.
In terms of how and why the extent tree block got corrupted, that is a
mystery. It could have been a memory corruption, due to hardware or
software bug in the kernel. It could be a disk corruption, again due
to hardware or software bug.
So we can note what happened, and see if we see anything else similar,
ut unless you can replicate it, I'm not sure we can do much more at
the moment.
Regardless, thank you for the report. We'll keep an eye out....
- Ted
next prev parent reply other threads:[~2012-07-31 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 2:17 Serious bug? Nelson, John R
2012-07-31 2:29 ` Eric Sandeen
2012-07-31 2:42 ` Theodore Ts'o [this message]
[not found] ` <0408C81F72528E40A0D3235A1F67FFC804A643@SN2PRD0202MB144.namprd02.prod.outlook.com>
[not found] ` <20120731032536.GE5027@thunk.org>
[not found] ` <0408C81F72528E40A0D3235A1F67FFC804A65F@SN2PRD0202MB144.namprd02.prod.outlook.com>
2012-07-31 21:38 ` Theodore Ts'o
2012-07-31 21:40 ` Eric Sandeen
2012-07-31 22:34 ` Theodore Ts'o
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=20120731024236.GB5027@thunk.org \
--to=tytso@mit.edu \
--cc=John_Nelson@student.uml.edu \
--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).