From: Eric Sandeen <sandeen@redhat.com>
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 21:29:47 -0500 [thread overview]
Message-ID: <5017431B.3080202@redhat.com> (raw)
In-Reply-To: <0408C81F72528E40A0D3235A1F67FFC804A61E@SN2PRD0202MB144.namprd02.prod.outlook.com>
On 7/30/12 9:17 PM, Nelson, John R wrote:
> Hi,
> I created a big 400GB file image and formatted it with mkfs.ext4. the format failed with
What kernel are you running on for starters? And how did you create that file image, is it sparse, preallocated, or pre-written?
> Warning: could not erase sector 2: Attempt to write block to filesystem resulted in short write
That's from zap-sector() in main(), happens very early, before much else goes on.
Does mkfs.ext4 -K (to prevent hole punching in the file) succeed?
-Eric
> Filesystem label=
> OS type: Linux
> Block size=4096 (log=2)
> Fragment size=4096 (log=2)
> Stride=0 blocks, Stripe width=0 blocks
> 26214400 inodes, 104857600 blocks
> 5242880 blocks (5.00%) reserved for the super user
> First data block=0
> Maximum filesystem blocks=4294967296
> 3200 block groups
> 32768 blocks per group, 32768 fragments per group
> 8192 inodes per group
> Superblock backups stored on blocks:
> 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
> 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
> 102400000
>
> Allocating group tables: done
> Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
> Warning: could not erase sector 0: Attempt to write block to filesystem resulted in short write
> mkfs.ext4: Attempt to write block to filesystem resulted in short write while zeroing block 104857584 at end of filesystem
> Writing inode tables: done
> Creating journal (32768 blocks): mkfs.ext4: Attempt to write block to filesystem resulted in short write
> while trying to create journal
> john@john-K53E:~$
>
> 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
snip
> [ 119.585130] EXT4-fs error (device sda3): ext4_ext_map_blocks:3769: inode #32243725: comm mkfs.ext4: bad extent address lblock: 108, depth: 2 pblock 0
>
> i deleted the image and rebooted and fsck was forced, but i didnt find any errors. But im not sure why this is happening. and please note this. the iblock in my log continues all the way down to 924.
>
> John Nelson
> --
> 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
>
next prev parent reply other threads:[~2012-07-31 2:29 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 [this message]
2012-07-31 2:42 ` Theodore Ts'o
[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=5017431B.3080202@redhat.com \
--to=sandeen@redhat.com \
--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).