public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	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:24:00 +0000	[thread overview]
Message-ID: <20020129142400.E1873@redhat.com> (raw)
In-Reply-To: <008f01c1a815$d8cdcc70$8a140237@rennes.si.fr.atosorigin.com> <20020129114222.B2298@redhat.com> <02c801c1a8cd$027ccd20$8a140237@rennes.si.fr.atosorigin.com>
In-Reply-To: <02c801c1a8cd$027ccd20$8a140237@rennes.si.fr.atosorigin.com>; from yann.morin.1998@anciens.enib.fr on Tue, Jan 29, 2002 at 02:58:20PM +0100

Hi,

On Tue, Jan 29, 2002 at 02:58:20PM +0100, Yann E. MORIN wrote:

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

Did you try a "dmesg"?

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

OK, that's certainly something I can try to reproduce --- ext3 over
loop over smbfs is not something which gets tested every day by the
ext3 developers. :-)

Cheers,
 Stephen

  reply	other threads:[~2002-01-29 14:24 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
2002-01-29 13:58   ` Yann E. MORIN
2002-01-29 14:24     ` Stephen C. Tweedie [this message]
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=20020129142400.E1873@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox