From: Eric Sandeen <sandeen@redhat.com>
To: Thiemo Nagel <thiemo.nagel@ph.tum.de>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: BUG at fs/ext4/mballoc.c:3295
Date: Thu, 12 Mar 2009 12:07:51 -0500 [thread overview]
Message-ID: <49B94167.4070409@redhat.com> (raw)
In-Reply-To: <49B93E44.8070109@ph.tum.de>
Thiemo Nagel wrote:
> Hello,
>
> the following can be observed reproducibly with 2.6.29-rc7 when filling
> up a very small (2MB) file system:
>
> dd if=/dev/zero of=/file/inside/small/filesystem
>
> hangs, dmesg output is:
>
> [ 602.831279] EXT4-fs: barriers enabled
> [ 602.862751] EXT4-fs warning: mounting fs with errors, running e2fsck
> is recommended
> [ 602.864165] kjournald2 starting: pid 5414, dev loop0:8, commit
> interval 5 seconds
> [ 602.864318] EXT4 FS on loop0, internal journal on loop0:8
> [ 602.864325] EXT4-fs: delayed allocation enabled
> [ 602.864348] EXT4-fs: file extents enabled
> [ 602.864669] EXT4-fs: mballoc enabled
> [ 602.864674] EXT4-fs: recovery complete.
> [ 602.869466] EXT4-fs: mounted filesystem loop0 with ordered data mode
> [ 623.000911] JBD: barrier-based sync failed on loop0:8 - disabling
> barriers
> [ 633.432299] ------------[ cut here ]------------
> [ 633.432329] kernel BUG at fs/ext4/mballoc.c:3295!
I don't see it:
# dd if=/dev/zero of=2mbfile bs=1M count=2
# mkfs.ext4 -F 2mbfile
# mount -o loop 2mbfile mnt/
# dd if=/dev/zero of=mnt/file
dd: writing to `mnt/file': No space left on device
1917+0 records in
1916+0 records out
980992 bytes (981 kB) copied, 0.0162723 s, 60.3 MB/s
is this more or less what you did?
-Eric
next prev parent reply other threads:[~2009-03-12 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 16:54 BUG at fs/ext4/mballoc.c:3295 Thiemo Nagel
2009-03-12 17:07 ` Eric Sandeen [this message]
2009-03-12 17:13 ` Thiemo Nagel
2009-03-12 17:16 ` Eric Sandeen
2009-03-12 18:46 ` [PATCH] fix bogus BUG_ONs in in mballoc code Eric Sandeen
2009-03-13 0:38 ` Theodore Tso
2009-03-13 11:09 ` Andreas Dilger
2009-03-13 1:09 ` Theodore Tso
2009-03-13 2:08 ` Eric Sandeen
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=49B94167.4070409@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=thiemo.nagel@ph.tum.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 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).