From: Frederic Weisbecker <fweisbec@gmail.com>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reiserfs deadlock in 2.6.36
Date: Wed, 22 Dec 2010 19:04:30 +0100 [thread overview]
Message-ID: <20101222180428.GD1739@nowhere> (raw)
In-Reply-To: <201012221850.51242.roucaries.bastien@gmail.com>
On Wed, Dec 22, 2010 at 06:50:48PM +0100, Bastien ROUCARIES wrote:
> Le jeudi 16 décembre 2010 14:49:48, Bastien ROUCARIES a écrit :
> > Le jeudi 2 décembre 2010 18:43:32, vous avez écrit :
> > > On Fri, Nov 26, 2010 at 05:57:05PM +0100, Bastien ROUCARIES wrote:
> > > > Dear frederic,
> I achieve to reproduce it. BTW it is my home partition with acl enable
How do you know you reproduced it? You had a crash before using SysRq?
Or you felt a deadlock or so?
What's interesting is that report is that there is no blocked task
that holds the reiserfs lock.
So I really feel the problem is that someone opened the journal but did not
release it.
How hard is it to reproduce now? If it's not so hard or haphazard, we should
start a bisection. Otherwise I think we'll need to do some tracing and this
is going to take several tries :)
next prev parent reply other threads:[~2010-12-22 18:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 15:49 Reiserfs deadlock in 2.6.36 Bastien ROUCARIES
2010-11-18 16:30 ` Frederic Weisbecker
2010-11-18 22:02 ` Bastien ROUCARIES
2010-11-26 16:57 ` Bastien ROUCARIES
2010-11-26 17:27 ` Bastien ROUCARIES
2010-12-02 17:43 ` Frederic Weisbecker
2010-12-16 13:49 ` Bastien ROUCARIES
2010-12-22 17:50 ` Bastien ROUCARIES
2010-12-22 18:04 ` Frederic Weisbecker [this message]
2010-12-22 18:11 ` Bastien ROUCARIES
2010-12-23 3:42 ` Frederic Weisbecker
2011-01-30 0:08 ` Bastien ROUCARIES
2011-02-16 16:22 ` Regression with dataloss: Reiserfs deadlock in 2.6.36 and 2.6.37, know working 2.6.33 Bastien ROUCARIES
2011-02-16 16:55 ` Frederic Weisbecker
2011-02-23 10:15 ` Bastien ROUCARIES
2011-03-02 12:49 ` Bastien ROUCARIES
2011-03-07 19:00 ` Reiserfs deadlock in 2.6.36 Frederic Weisbecker
2011-03-08 8:41 ` Bastien ROUCARIES
2011-03-08 14:05 ` Frederic Weisbecker
2011-03-08 15:21 ` Bastien ROUCARIES
2011-03-08 14:18 ` Frederic Weisbecker
2011-03-08 15:22 ` Bastien ROUCARIES
2011-03-28 9:14 ` Bastien ROUCARIES
2011-03-31 15:04 ` Bastien ROUCARIES
2011-04-05 13:30 ` Bastien ROUCARIES
2011-04-05 15:58 ` Jeff Mahoney
2011-04-05 16:10 ` Bastien ROUCARIES
2011-04-05 22:58 ` Frederic Weisbecker
2011-04-06 10:14 ` Bastien ROUCARIES
2011-04-11 8:40 ` Bastien ROUCARIES
2011-04-11 8:49 ` Bastien ROUCARIES
2011-04-11 8:49 ` Bastien ROUCARIES
2011-04-11 23:18 ` Frederic Weisbecker
2011-04-12 12:01 ` Bastien ROUCARIES
2011-04-18 8:01 ` Bastien ROUCARIES
2011-04-26 15:29 ` Frederic Weisbecker
2011-04-27 11:08 ` Bastien ROUCARIES
2011-04-27 11:10 ` Bastien ROUCARIES
2011-04-27 11:13 ` Bastien ROUCARIES
2011-04-27 12:34 ` solsTiCe d'Hiver
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=20101222180428.GD1739@nowhere \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roucaries.bastien@gmail.com \
/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