From: ptb@lab.it.uc3m.es (Peter T. Breuer)
To: linux-raid@vger.kernel.org
Subject: Re: No response?
Date: Thu, 20 Jan 2005 19:12:40 +0100 [thread overview]
Message-ID: <ot85c2-es9.ln1@news.it.uc3m.es> (raw)
In-Reply-To: Pine.LNX.4.58.0501201052240.19586@lewis.et.byu.edu
David Dougall <davidd@et.byu.edu> wrote:
> If I am running software raid1 and a disk device starts throwing I/O
> errors, Is the filesystem supposed to see any indication of this? I
No - not if the error is on only one disk. The first error will fault
the disk from the array and the driver will retry the read, and must
retry from another disk (the first is no longer there).
The actual i/o to the disks does not form part of the i/o to the raid
array itself, so there is little chance of contamination between the
two. The raid i/o is only acked back to the user when one of the disk
i/o's (on read) has succeeded.
> thought software raid would mask all of this and just fail the drive.
>
> I have servers with xfs as the filesystem and xfs will start to throw I/O
> errors when a disk starts acting up even with software raid in between.
That's strange. But not impossible - coding for error situations is
always difficult, and more difficult to test.
> If it makes a difference, I am running linux-2.4.26
Peter
next prev parent reply other threads:[~2005-01-20 18:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 17:55 No response? David Dougall
2005-01-20 18:12 ` Peter T. Breuer [this message]
2005-01-20 18:14 ` Gordon Henderson
2005-01-20 18:37 ` Mark Bellon
2005-01-20 19:15 ` David Dougall
2005-01-20 19:35 ` Mark Bellon
2005-01-20 19:37 ` Gordon Henderson
2005-01-20 19:41 ` Mark Bellon
2005-01-20 19:49 ` David Dougall
2005-01-20 18:21 ` Mike Hardy
2005-01-20 18:30 ` Mario Holbe
2005-01-20 18:57 ` David Dougall
2005-01-20 19:12 ` Kanoa Withington
2005-01-20 19:17 ` David Dougall
2005-01-20 19:23 ` Guy
2005-01-20 19:34 ` Kanoa Withington
2005-01-20 19:44 ` Mark Bellon
2005-01-20 19:18 ` Guy
2005-01-20 19:24 ` Peter T. Breuer
2005-01-20 19:51 ` David Dougall
2005-01-20 19:28 ` Mark Bellon
2005-01-20 18:49 ` Kanoa Withington
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=ot85c2-es9.ln1@news.it.uc3m.es \
--to=ptb@lab.it.uc3m.es \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).