mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: "Stephen C. Tweedie" <sct@redhat.com>
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 14:58:20 +0100	[thread overview]
Message-ID: <02c801c1a8cd$027ccd20$8a140237@rennes.si.fr.atosorigin.com> (raw)
In-Reply-To: <008f01c1a815$d8cdcc70$8a140237@rennes.si.fr.atosorigin.com> <20020129114222.B2298@redhat.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

Hi Stephen! Hi lists!

> > 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?

No. This is the only one. Even when I enter 'reboot' and hit enter, it
just freezes without any message. For quite a while (more than 5').
Nothing more appears, niether on screen nor on my serial console.

> 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.

That I tested. No bad block on the remote host (assertion happens
only when writing to a loop residing on a samba share, on a Win2k
host).

> Could you also please run ksymoops to decode the log trace?

Unfortunately no, I haven't got enough place on the machine to test
more than two kernel at a time. Now is time for the 2.4.18-pre7 with
the ext3 debug patch. But this one will get ksymoops run against.

Regards,
Yann.

PS. Because I'm  often away from work in these days, and because my
test machine is a plain old Pentium Pro, I can't do tests as often as
I might want to... Please forgive slowliness...
YEM.

PPS. I'm not subscribed to ext2-devel, please copy me (or lkml).
YEM.

--
.---------------------------.----------------------.------------------.
|       Yann E. MORIN       |  Real-Time Embedded  | ASCII RIBBON /"\ |
| Phone: (33/0) 662 376 056 |  Software  Designer  |   CAMPAIGN   \ / |
|   http://ymorin.free.fr   °----------------------:   AGAINST     X  |
| yann.morin.1998@anciens.enib.fr                  |  HTML MAIL   / \ |
°--------------------------------------------------°------------------°




  reply	other threads:[~2002-01-29 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-28 16:07 Yann E. MORIN
2002-01-28 18:41 ` Andrew Morton
2002-01-29 11:42 ` Stephen C. Tweedie
2002-01-29 13:58   ` Yann E. MORIN [this message]
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='02c801c1a8cd$027ccd20$8a140237@rennes.si.fr.atosorigin.com' \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.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

all inboxes | Powered by JetHome®