linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "NeilBrown" <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, 23 Dec 2008 08:07:31 +1100 (EST)	[thread overview]
Message-ID: <8a3fbc034da936df0f430739bacbf28b.squirrel@neil.brown.name> (raw)
In-Reply-To: <cccedfc60812220640m53f668q56fcf765286bedd4@mail.gmail.com>

On Tue, December 23, 2008 1:40 am, Jon Nelson wrote:
> More updates:
>
> 1. I upgraded to openSUSE 11.1 over the weekend. The kernel is
> 2.6.27.7-9 as of this writing.
>
> 2. When I fired up the machine which hosts the network block device,
> the machine hosting the raid properly noticed and --re-added /dev/nbd0
> to /dev/md11.
>
> 3. /dev/md11 went into "recover" mode (not resync).
>
> 4. I'm using persistent metadata and a write-intent bitmap.
>

It does seem like you are doing the right thing....

Can you show me the output of both --examine and ----examine-bitmap
on both /dev/sda and /dev/nbd0 just before you --re-add nbd0 to
the array that already contains sda ??
For recovery to use the bitmap, "Events Cleared" on sda must be no
more than "Events" (from --examine) of nbd0.

What you sent doesn't quite have all this information, but it does
show that for nbd0 before it is added to the array:

--examine;
         Events : 7042

--examine-bitmap:
          Events : 5518
  Events Cleared : 5494

This shouldn't happen.  The 'events' from --examine and from
--examine-bitmap should always be the same.  That is how md knows
that the bitmap is still accurate.
This seems to suggest that nbd0 was, for a while, assembled into an
array which did not have an active bitmap.

Thanks,
NeilBrown



  reply	other threads:[~2008-12-22 21:07 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
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 [this message]
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=8a3fbc034da936df0f430739bacbf28b.squirrel@neil.brown.name \
    --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).