From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: lkml <linux-kernel@vger.kernel.org>, ext2-devel@lists.sourceforge.net
Subject: Re: Assertion failure / do_get_write_acess() / loop / samba
Date: Tue, 29 Jan 2002 11:42:22 +0000 [thread overview]
Message-ID: <20020129114222.B2298@redhat.com> (raw)
In-Reply-To: <008f01c1a815$d8cdcc70$8a140237@rennes.si.fr.atosorigin.com>
In-Reply-To: <008f01c1a815$d8cdcc70$8a140237@rennes.si.fr.atosorigin.com>; from yann.morin.1998@anciens.enib.fr on Mon, Jan 28, 2002 at 05:07:12PM +0100
Hi,
On Mon, Jan 28, 2002 at 05:07:12PM +0100, Yann E. MORIN wrote:
>
> I've encountered a reproductible 'Assertion failure' in 2.4.17.
> It happens on pure vanilla, as well as on sched O1-J0, and also on
> I'm able to write a bit of data on it (about a few Mib), and then I
> got this Assertion failure:
>
> --8<-- Begin --8<--
> Assertion failure in do_get_write_access() at transaction.c:728:
> "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)"
Are there any other log messages in the kernel log?
The only easy way I can see for this to be triggered is if there is a
bad block on disk being accessed. That ought to appear in the log.
Could you also please run ksymoops to decode the log trace?
Cheers,
Stephen
next prev parent reply other threads:[~2002-01-29 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 16:07 Assertion failure / do_get_write_acess() / loop / samba Yann E. MORIN
2002-01-28 18:41 ` Andrew Morton
2002-01-29 11:42 ` Stephen C. Tweedie [this message]
2002-01-29 13:58 ` Yann E. MORIN
2002-01-29 14:24 ` Stephen C. Tweedie
2002-01-29 15:40 ` Yann E. MORIN
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=20020129114222.B2298@redhat.com \
--to=sct@redhat.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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.