linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: LinuxRaid <linux-raid@vger.kernel.org>
Subject: Re: weird issues with raid1
Date: Tue, 16 Dec 2008 12:21:42 +1100	[thread overview]
Message-ID: <18759.678.74091.236787@notabene.brown> (raw)
In-Reply-To: message from Jon Nelson on Monday December 15

On Monday December 15, jnelson-linux-raid@jamponi.net wrote:
> On Mon, Dec 15, 2008 at 3:33 PM, Neil Brown <neilb@suse.de> wrote:
> > On Monday December 15, jnelson-linux-raid@jamponi.net wrote:
> >>
> >> Aha!  This explains a question I raised in another email. What
> >> happened there is a previously fully active member of the raid got
> >> added, somehow, as a spare, via --incremental. That's when the entire
> >> raid thought it needed to be rebuilt. How did that (the device being
> >> treated as a spare instead of as a previously fully active member)
> >> happen?
> >
> > It is hard to guess without details, and they might be hard to collect
> > after the fact.
> > Maybe if you have the kernel logs of when the server rebooted and the
> > recovery started, that might contain some hints.
> 
> I hope this helps.

Yes it does, though I generally prefer to get more complete logs.  If
I get the surrounding log lines then I know what isn't there as well
as what is - and it isn't always clear at first which bits will be
important. 

The problem here is that --incremental doesn't provide the --re-add
functionality that you are depending on.  That was an oversight on my
part.  I'll see if I can get it fixed.
In the mean time, you'll need to use --re-add (or --add, it does the
same thing in your situation) to add nbd0 to the array.

NeilBrown


> 
> Prior to the reboot:
> 
> Dec 15 15:19:39 turnip kernel: md: md11: recovery done.
> Dec 15 15:19:39 turnip kernel: RAID1 conf printout:
> Dec 15 15:19:39 turnip kernel:  --- wd:2 rd:2
> Dec 15 15:19:39 turnip kernel:  disk 0, wo:0, o:1, dev:nbd0
> Dec 15 15:19:39 turnip kernel:  disk 1, wo:0, o:1, dev:sda
> 
> During booting:
> 
> <6>raid1: raid set md11 active with 1 out of 2 mirrors
> <6>md11: bitmap initialized from disk: read 1/1 pages, set 1 bits
> <6>created bitmap (10 pages) for device md11
> 
> After boot:
> 
> Dec 15 15:34:38 turnip kernel: md: bind<nbd0>
> Dec 15 15:34:38 turnip kernel: RAID1 conf printout:
> Dec 15 15:34:38 turnip kernel:  --- wd:1 rd:2
> Dec 15 15:34:38 turnip kernel:  disk 0, wo:1, o:1, dev:nbd0
> Dec 15 15:34:38 turnip kernel:  disk 1, wo:0, o:1, dev:sda
> Dec 15 15:34:38 turnip kernel: md: recovery of RAID array md11
> Dec 15 15:34:38 turnip kernel: md: minimum _guaranteed_  speed: 1000
> KB/sec/disk.
> Dec 15 15:34:38 turnip kernel: md: using maximum available idle IO
> bandwidth (but not more than 200000 KB/sec) for recovery.
> Dec 15 15:34:38 turnip kernel: md: using 128k window, over a total of
> 78123988 blocks.
> 
> /dev/nbd0 was added via --incremental (mdadm 3.0)
> 

  reply	other threads:[~2008-12-16  1:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06  2:10 weird issues with raid1 Jon Nelson
2008-12-06  2:46 ` Jon Nelson
2008-12-06 12:16   ` Justin Piszcz
2008-12-15  2:17     ` Jon Nelson
2008-12-15  6:00 ` Neil Brown
2008-12-15 13:42   ` Jon Nelson
2008-12-15 21:33     ` Neil Brown
2008-12-15 21:47       ` Jon Nelson
2008-12-16  1:21         ` Neil Brown [this message]
2008-12-16  2:32           ` Jon Nelson
2008-12-18  4:42           ` Neil Brown
2008-12-18  4:50             ` Jon Nelson
2008-12-18  4:55               ` Jon Nelson
2008-12-18  5:17                 ` Neil Brown
2008-12-18  5:47                   ` Jon Nelson
2008-12-18  6:21                     ` Neil Brown
2008-12-19  2:15                       ` Jon Nelson
2008-12-19 16:51                         ` Jon Nelson
2008-12-19 20:40                           ` Jon Nelson
2008-12-19 21:18                             ` Jon Nelson
2008-12-22 14:40                               ` Jon Nelson
2008-12-22 21:07                                 ` NeilBrown
2008-12-18  5:43   ` Neil Brown
2008-12-18  5:54     ` Jon Nelson

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=18759.678.74091.236787@notabene.brown \
    --to=neilb@suse.de \
    --cc=jnelson-linux-raid@jamponi.net \
    --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).