mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jasper Spaans <jasper@spaans.ds9a.nl>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] raid5 crash with 2.4.0-test12 [Was: Linux-2.4.0-test12]
Date: Tue, 12 Dec 2000 21:07:48 +0100	[thread overview]
Message-ID: <20001212210748.C12995@spaans.ds9a.nl> (raw)
In-Reply-To: <20001212160605.A1835@spaans.ds9a.nl> <Pine.LNX.4.10.10012121047140.2239-100000@penguin.transmeta.com> <14902.33510.300257.269105@notabene.cse.unsw.edu.au>
In-Reply-To: <14902.33510.300257.269105@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Wed, Dec 13, 2000 at 06:56:22AM +1100

On Wed, Dec 13, 2000 at 06:56:22AM +1100, Neil Brown wrote:

> Guilt by association :-)
> 
> What this bit of code (complete_stripe/raid5_end_buffer_io) is doing
> is observing that it as completed some I/O request that was made of
> the raid5 device and is calling the b_end_io on the buffer_head that
> is was passed.  So it is not one of raid5's buffers that has the bad
> b_end_io, but someone else's buffer that raid5 was asked to service.
> 
> You say "things with a mysql-db on a raid5-device".  Can I interpret
> this to mean that mysql was talking driectly to /dev/md0, or is there
> some filesystem in-between?
> Either way, I expect Linus' suggestion will provide the answer.

Will try to reproduce this, with Linus' suggestion; btw, this mysql-db is
running on ext2, nothing exotic.

Regards,
-- 
  Q_.        Jasper Spaans  <mailto:jspaans@mediakabel.nl>        -o)
 `~\         Conditional Access/DVB-C/OpenTV/Unix-adviseur        /\\
Mr /\                                                            _\_v
Zap     Een ongezellig dure consultant nodig? Mail sales@insultant.nl
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-12 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12  2:52 Linux-2.4.0-test12 Linus Torvalds
2000-12-12 15:06 ` [BUG] raid5 crash with 2.4.0-test12 [Was: Linux-2.4.0-test12] Jasper Spaans
2000-12-12 19:06   ` Linus Torvalds
2000-12-12 19:56     ` Neil Brown
2000-12-12 20:07       ` Jasper Spaans [this message]
2000-12-12 22:41     ` Jasper Spaans
2000-12-12 23:21       ` Neil Brown
2000-12-12 23:47         ` Linus Torvalds
2000-12-13  0:17           ` Neil Brown
2000-12-13  3:08             ` Linus Torvalds
2000-12-13 11:52               ` Jasper Spaans
2000-12-13 23:15               ` Neil Brown

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=20001212210748.C12995@spaans.ds9a.nl \
    --to=jasper@spaans.ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=torvalds@transmeta.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®