All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Clements <Paul.Clements@SteelEye.com>
To: Jeroen Baten <jbaten@i2rs.nl>
Cc: linux-raid@vger.kernel.org
Subject: Re: question regarding a raid-1 set
Date: Tue, 26 Aug 2003 12:11:37 -0400	[thread overview]
Message-ID: <3F4B86B9.A1125164@SteelEye.com> (raw)
In-Reply-To: 200308261800.28078.jbaten@i2rs.nl

Jeroen Baten wrote:
 
> Well.... If you really like to know (I would really apreciate it!) this is the
> bootlog (bare in mind there are 3 raid-1 arrays):

Looks like md is confused because sdb6 is in slot 1. So the hot-remove,
hot-add should get you back up and running (hot-add will put the disk
back in slot 2, which should make md happy).

--
Paul


> <6>md:  adding sdb6 ...
> <6>md:  adding sda6 ...
> <6>md: created md2
> <6>md: bind<sda6,1>
> <6>md: bind<sdb6,2>
> <6>md: running: <sdb6><sda6>
> <6>md: sdb6's event counter: 00000028
> <6>md: sda6's event counter: 00000028
> <6>md: RAID level 1 does not need chunksize! Continuing anyway.
> <6>md2: max total readahead window set to 508k
> <6>md2: 1 data-disks, max readahead per data-disk: 508k
> <3>raid1: disabled mirror sdb6 (not in sync)
> <6>raid1: device sda6 operational as mirror 0
> <1>raid1: md2, not all disks are operational -- trying to recover array
> <6>raid1: raid set md2 active with 1 out of 2 mirrors
> <6>md: recovery thread got woken up ...
> <3>md2: no spare disk to reconstruct array! -- continuing in degraded mode
> <6>md: recovery thread finished ...

      reply	other threads:[~2003-08-26 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-26 14:37 question regarding a raid-1 set Jeroen Baten
2003-08-26 15:11 ` Martin K. Petersen
2003-08-26 15:44   ` Paul Clements
2003-08-26 16:00     ` Jeroen Baten
2003-08-26 16:11       ` Paul Clements [this message]

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=3F4B86B9.A1125164@SteelEye.com \
    --to=paul.clements@steeleye.com \
    --cc=jbaten@i2rs.nl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.