From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13369] kernel BUG at fs/ext4/inode.c:3123
Date: Sun, 24 May 2009 18:28:23 GMT [thread overview]
Message-ID: <200905241828.n4OISN1R025683@demeter.kernel.org> (raw)
In-Reply-To: <bug-13369-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13369
--- Comment #11 from Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> 2009-05-24 18:28:23 ---
On Sun, May 24, 2009 at 02:52:48AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13369
>
>
> Theodore Tso <tytso@mit.edu> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |tytso@mit.edu
>
>
>
>
> --- Comment #5 from Theodore Tso <tytso@mit.edu> 2009-05-24 02:52:48 ---
> So I'm glad you're using a filesystem with a 1k blocksize since it provides a
> good test case for us --- and we don't do enough testing for the case where the
> blocksize != pagesize. But you do realize that the ext4 filesystem will be
> far more efficient with the larger 4k blocksize, right?
>
> I'm not able to reproduce the problem on a filesystem with 1k blocksize running
> fsx, fsstress, and dbench using a 2.6.30-rc6 kernel with the full ext4 patch
> queue, using a netbook with an dual-core N270 Atom processor. I'm retrying
> with a stock 2.6.30-rc6 kernel now...
>
It is with nodelalloc. I am also finding some unmapped buffer_heads in
nodelalloc mode with data=journal. See the latest update for bug
http://bugzilla.kernel.org/show_bug.cgi?id=12624
-aneesh
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-05-24 18:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 12:04 [Bug 13369] New: kernel BUG at fs/ext4/inode.c:3123 bugzilla-daemon
2009-05-23 12:07 ` [Bug 13369] " bugzilla-daemon
2009-05-23 15:06 ` bugzilla-daemon
2009-05-23 21:40 ` bugzilla-daemon
2009-05-24 18:27 ` Aneesh Kumar K.V
2009-05-23 21:46 ` bugzilla-daemon
2009-05-24 2:52 ` bugzilla-daemon
2009-05-24 18:28 ` Aneesh Kumar K.V
2009-05-24 5:08 ` bugzilla-daemon
2009-05-24 12:02 ` bugzilla-daemon
2009-05-24 12:03 ` bugzilla-daemon
2009-05-24 16:32 ` bugzilla-daemon
2009-05-24 18:27 ` bugzilla-daemon
2009-05-24 18:28 ` bugzilla-daemon [this message]
2009-05-24 19:20 ` Aneesh Kumar K.V
2009-05-24 19:20 ` bugzilla-daemon
2009-05-26 13:16 ` Aneesh Kumar K.V
2009-05-24 20:43 ` bugzilla-daemon
2009-05-24 20:44 ` bugzilla-daemon
2009-05-26 13:16 ` bugzilla-daemon
2009-05-27 21:32 ` bugzilla-daemon
2009-08-18 17:38 ` bugzilla-daemon
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=200905241828.n4OISN1R025683@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).