From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Paul Clements <paul.clements@steeleye.com>
Cc: neilb@cse.unsw.edu.au, linux-raid@vger.kernel.org
Subject: Re: Problem with raid1 read error patch
Date: Mon, 20 Sep 2004 18:14:27 +0200 [thread overview]
Message-ID: <1095696866.8380.23.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <414EF709.7040505@steeleye.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Mon, 2004-09-20 at 17:28, Paul Clements wrote:
Hi Paul
> > After backing that patch out, with some minor modifications because the
> > code has changed a little bit, I get a number of scsi-errors and after a
> > while the drive gets disabled like above but life continues like before
> > the patch went in. That is, no infinite loop and everything works :)
> >
> > Any ideas to what went wrong?
>
> Yes. You're getting the infinite retries because the BIO_UPTODATE flag
> in the bio is not set.
Ah
> I've been debugging the same problem just recently. In addition to this
> patch from Neil, you'll also need a patch that I posted here last week,
> which does a bio_put() and a bio_clone() to get rid of the old bio that
> the read error occurred on, and create a new (clean) bio to retry the
> read against:
>
> http://marc.theaimsgroup.com/?l=linux-raid&m=109527014728404&w=2
Thanks, will try it out tomorrow when I'm back in front of the machine.
Didn't expect an answer so soon :)
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-20 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 15:16 Problem with raid1 read error patch Martin Josefsson
2004-09-20 15:28 ` Paul Clements
2004-09-20 16:14 ` Martin Josefsson [this message]
2004-09-21 16:07 ` Martin Josefsson
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=1095696866.8380.23.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=paul.clements@steeleye.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