linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
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-20090310: ext4 hangs
Date: Tue, 10 Mar 2009 11:47:45 -0400	[thread overview]
Message-ID: <20090310154745.GF23075@mit.edu> (raw)
In-Reply-To: <a4423d670903100718w1a532143he767782ae598d0fb@mail.gmail.com>

On Tue, Mar 10, 2009 at 05:18:55PM +0300, Alexander Beregalov wrote:
> > Thanks for reporting this; does it show up on stock 2.6.29-rc7?
> No, I can not reproduce it.
> It is a slow system, I would not like to bisect it, only if it is the
> last possibility.

Just to be clear; you weren't able to reproduce it on stock 2.6.29-rc7
---- does it reproduce easily on linux-next?

Next question --- does the system hang completely, or just the dbench
process (and probably any process that tries touching the filesystem
that's hung up)?  Do you have a serial console, or someone of
recording all of the dumps coming from sysrq-t?  The two stack traces
you gave weren't the ones causing the problem, but rather the ones
waiting for the journal lock.  

I don't think is related to BZ #12579, although some of the symptoms
look superficially the same.

							- Ted

P.S.  What are your dbench parameters, and how big is your filesystem,
so I can try to reproduce it on my side?  And how long do you
typically need to run before this triggers?  Thanks!

  reply	other threads:[~2009-03-10 15:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 12:17 next-20090310: ext4 hangs Alexander Beregalov
2009-03-10 12:46 ` Theodore Tso
2009-03-10 12:54   ` Alexander Beregalov
2009-03-10 14:18   ` Alexander Beregalov
2009-03-10 15:47     ` Theodore Tso [this message]
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=20090310154745.GF23075@mit.edu \
    --to=tytso@mit.edu \
    --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 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).