linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Pretorious <eric@pretorious.net>
To: linux-raid@vger.kernel.org
Cc: Mike V <mike@asacomputers.com>,
	tech@asacomputers.com, Dinesh <dinesh@asacomputers.com>
Subject: Re: linux-raid compatable w/ Adaptec AIC-7902?
Date: Wed, 29 Jun 2005 18:08:54 -0700	[thread overview]
Message-ID: <200506291808.54549.eric@pretorious.net> (raw)
In-Reply-To: <200506291738.30516.eric@pretorious.net>

On Wednesday 29 June 2005 05:38 pm, Eric Pretorious wrote:
>So it would appear that sda7 has failed. Is that correct?

I was in the process of reading this portion of /var/log/messages...

>SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 10000
>I/O error: dev 08:07, sector 2980224
>raid1: disk failure on sda7, disabling device.
>	Operation continuing on 1 devices
>raid1: mirro resync was not fully finished, restarting next time.
>md4: no spare disk to reconstruct array! -- continuing in degraded mode
>md: md_do_sync() got signal ... exiting
>  ...
>md: autorun
>md: considering sdb7 ...
>md:  adding sdb7 ...
>md:  adding sdb7 ...
>md: created md4
>md: bind<sda7,1>
>md: bind<sdb7,2>
>md: running: <sdb7><sda7>
>md: sdb7's event counter: 0000002b
>md: sda7's event counter: 0000002a
>md: superblcokc update time inconsistency -- using the most recent one
>md: freshest: sdb7
>md4: kicking faulty sda7! 
>md: unbind<sda7,1>
>md: export rdev(sda7)
>mf: md4: raid array is not clean -- starting background reconstruction

...when the system choked, again.  Ug!

I expected that a mirror would be more robust than to bring-down the entire 
system when one RAID member fails. Was this assumption incorrect?

-- 
Eric P.,
Truckee, CA

  reply	other threads:[~2005-06-30  1:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-29 22:38 linux-raid compatable w/ Adaptec AIC-7902? Eric Pretorious
2005-06-29 22:57 ` Eric Pretorious
2005-06-29 23:57   ` Eric Pretorious
2005-06-29 23:55 ` Eric Pretorious
2005-06-30  2:10   ` Guy
2005-06-30 17:14     ` Eric Pretorious
2005-07-04 11:27       ` Turbo Fredriksson
2005-07-07 18:49         ` Eric Pretorious
2005-07-08  0:35           ` Mathieu Chouquet-Stringer
2005-07-08 12:40           ` Turbo Fredriksson
2005-07-08 12:52             ` Joshua Baker-LePain
2005-07-08 22:56               ` Mark Hahn
2005-07-08 23:20                 ` Tyler
2005-06-30  0:38 ` Eric Pretorious
2005-06-30  1:08   ` Eric Pretorious [this message]
2005-06-30 15:51     ` Dinesh

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=200506291808.54549.eric@pretorious.net \
    --to=eric@pretorious.net \
    --cc=dinesh@asacomputers.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mike@asacomputers.com \
    --cc=tech@asacomputers.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;
as well as URLs for NNTP newsgroup(s).