From: "Stephen C. Tweedie" <sct@redhat.com>
To: Pascal Schmidt <der.eremit@email.de>
Cc: Andrew Morton <akpm@osdl.org>,
"Marcelo W. Tosatti" <marcelo@conectiva.com.br>,
linux-kernel <linux-kernel@vger.kernel.org>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: [2.4.22-rc1] ext3/jbd assertion failure transaction.c:1164
Date: 28 Aug 2003 22:19:09 +0100 [thread overview]
Message-ID: <1062105549.17230.421.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308281555540.1044-100000@neptune.local>
Hi,
On Thu, 2003-08-28 at 14:57, Pascal Schmidt wrote:
> > Many thanks --- I was able to reproduce this very easily, and I know of
> > one or two very unusual things that fsx does which might well be the
> > trigger here. I'll let you know how things go.
>
> Good, at least it's not a bug that only happens here and is hard to
> reproduce elsewhere.
>
> I hope this does not happen under normal fs usage. ;)
It's all down to ext3_writepage() using data-journaling rather than
metadata journaling.
The obvious fix is just to make the journal_dirty_async_data() code
commit its writes as metadata if the inode is marked for
data-journaling, and to set the transaction handle to be synchronous in
that case. Sounds like a recipe for deadlock if done incorrectly,
though, so I'll give it a more careful look tomorrow.
Cheers,
Stephen
next prev parent reply other threads:[~2003-08-28 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0308262241580.2728-300000@neptune.local>
2003-08-28 11:15 ` Stephen C. Tweedie
2003-08-28 13:57 ` Pascal Schmidt
2003-08-28 21:19 ` Stephen C. Tweedie [this message]
2003-09-12 12:12 ` Marcelo Tosatti
2003-08-24 20:57 Pascal Schmidt
2003-08-26 12:15 ` Marcelo Tosatti
2003-08-26 15:04 ` Pascal Schmidt
2003-08-26 15:57 ` Pascal Schmidt
2003-08-26 16:15 ` Pascal Schmidt
2003-08-26 18:51 ` Stephen C. Tweedie
2003-08-26 22:48 ` Lorenzo Allegrucci
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=1062105549.17230.421.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=akpm@osdl.org \
--cc=der.eremit@email.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®