linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Beregalov <a.beregalov@gmail.com>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: next-20090310: ext4 hangs
Date: Tue, 10 Mar 2009 15:17:51 +0300	[thread overview]
Message-ID: <a4423d670903100517y42f342d4pd73c4c36f5c64dd7@mail.gmail.com> (raw)

Hi

It is similar to http://lkml.org/lkml/2009/2/6/304,
http://bugzilla.kernel.org/show_bug.cgi?id=12579


I run dbench on ext4 on loop on ext3 on sparc.
The kernel is 2.6.29-rc7-next-20090310
e2fsprogs -1.41.4

ioctl32(mkfs.ext4:1668): Unknown cmd fd(3) cmd(40041272){t:12;sz:4}
arg(ffb2ce60) on /testfs
ioctl32(mkfs.ext4:1668): Unknown cmd fd(3) cmd(20001260){t:12;sz:0}
arg(ffb2ce6c) on /testfs
ioctl32(mkfs.ext4:1668): Unknown cmd fd(3) cmd(401c0204){t:02;sz:28}
arg(ffb2ce44) on /testfs
ioctl32(mkfs.ext4:1668): Unknown cmd fd(3) cmd(20001268){t:12;sz:0}
arg(ffb2d564) on /testfs
ioctl32(mkfs.ext4:1668): Unknown cmd fd(3) cmd(2000125e){t:12;sz:0}
arg(ffb2ce6c) on /testfs
EXT4-fs: barriers enabled
EXT4 FS on loop0, internal journal on loop0:8
EXT4-fs: delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs: mounted filesystem loop0 with ordered data mode
kjournald2 starting: pid 1672, dev loop0:8, commit interval 5 seconds
JBD: barrier-based sync failed on loop0:8 - disabling barriers
INFO: task kjournald2:1672 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kjournald2    D 0000000000557a0c     0  1672      2
Call Trace:
 [0000000000768bcc] schedule+0x18/0x40
 [0000000000557a0c] jbd2_journal_commit_transaction+0x208/0x1718
 [000000000055d758] kjournald2+0x14c/0x318
 [0000000000465d34] kthread+0x48/0x7c
 [000000000042b364] kernel_thread+0x3c/0x54
 [0000000000465c88] kthreadd+0xc8/0x12c
INFO: lockdep is turned off.
INFO: task dbench:1674 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
dbench        D 000000000055716c     0  1674   1673
Call Trace:
 [0000000000768bcc] schedule+0x18/0x40
 [000000000055716c] start_this_handle+0x374/0x508
 [0000000000557500] jbd2_journal_start+0xbc/0x11c
 [000000000053a438] ext4_journal_start_sb+0x5c/0x84
 [000000000052a9b8] ext4_dirty_inode+0xd4/0xf0
 [00000000004d1a14] __mark_inode_dirty+0x2c/0x188
 [00000000004c7714] touch_atime+0x160/0x178
 [00000000004c2a3c] vfs_readdir+0x88/0xb0
 [00000000004eab90] compat_sys_getdents+0x3c/0x8c
 [0000000000406154] linux_sparc_syscall32+0x34/0x40

             reply	other threads:[~2009-03-10 12:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 12:17 Alexander Beregalov [this message]
2009-03-10 12:46 ` next-20090310: ext4 hangs Theodore Tso
2009-03-10 12:54   ` Alexander Beregalov
2009-03-10 14:18   ` Alexander Beregalov
2009-03-10 15:47     ` Theodore Tso
2009-03-11 16:07       ` Alexander Beregalov
2009-03-25 15:11         ` Jan Kara
2009-03-25 15:15           ` Jan Kara
2009-03-25 15:18             ` Alexander Beregalov
2009-03-25 15:22               ` Jan Kara
2009-03-25 15:29                 ` Alexander Beregalov
2009-03-25 16:15                   ` Jan Kara
2009-03-25 17:07                     ` Alexander Beregalov
2009-03-25 19:43                       ` Jan Kara
2009-03-25 22:38                         ` Alexander Beregalov
2009-03-26  0:00                           ` Jan Kara
2009-03-26  0:17                             ` Jiri Gaisler
2009-03-26  0:25                               ` Jan Kara
2009-03-31 10:01                           ` Jan Kara
2009-03-31 10:07                             ` Alexander Beregalov
2009-03-31 12:33                               ` Jan Kara
2009-04-02 18:50                                 ` Alexander Beregalov
2009-04-04 21:09                                   ` Alexander Beregalov
2009-04-06  9:20                                     ` Jan Kara

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=a4423d670903100517y42f342d4pd73c4c36f5c64dd7@mail.gmail.com \
    --to=a.beregalov@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).