From: Eric Sandeen <sandeen@redhat.com>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
linux-ext4@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: next-20090206: deadlock on ext4
Date: Fri, 06 Feb 2009 14:07:18 -0600 [thread overview]
Message-ID: <498C9876.3060208@redhat.com> (raw)
In-Reply-To: <a4423d670902061004i424817e1vd699a61e335f010a@mail.gmail.com>
Alexander Beregalov wrote:
> 2009/2/6 Eric Sandeen <sandeen@redhat.com>:
>> Alexander Beregalov wrote:
>>> Hi
>>>
>>> I run dbench on ext4 on loop device.
>>>
>>> EXT4-fs: barriers enabled
>>> kjournald2 starting: pid 2420, dev loop0:8, commit interval 5 seconds
>>> 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
>>> JBD: barrier-based sync failed on loop0:8 - disabling barriers
>>>
>>> INFO: task pdflush:2339 blocked for more than 120 seconds.
>> Looks a lot like a bug I filed:
>>
>> http://bugzilla.kernel.org/show_bug.cgi?id=12579
>>
>> but I'm having trouble reproducing it, now. I'll try dbench!
> Yes, I can reproduce it easy with dbench.
Do you only hit it on loopback? What is the filesystem hosting the loop
file?
Thanks,
-Eric
next prev parent reply other threads:[~2009-02-06 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 17:35 next-20090206: deadlock on ext4 Alexander Beregalov
2009-02-06 17:42 ` Eric Sandeen
2009-02-06 18:04 ` Alexander Beregalov
2009-02-06 20:07 ` Eric Sandeen [this message]
2009-02-09 12:01 ` Alexander Beregalov
2009-02-13 22:21 ` Eric Sandeen
2009-02-18 9:56 ` Alexander Beregalov
2009-02-18 10:12 ` Ralf Hildebrandt
2009-02-18 13:04 ` Theodore Tso
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=498C9876.3060208@redhat.com \
--to=sandeen@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.