linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nate Dailey <nate.dailey@stratus.com>
To: Brassow Jonathan <jbrassow@redhat.com>,
	device-mapper development <dm-devel@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [dm-devel] [PATCH] dm-raid: check events in super_validate
Date: Wed, 26 Feb 2014 19:17:28 -0500	[thread overview]
Message-ID: <530E8418.50707@stratus.com> (raw)
In-Reply-To: <4A643D2E-04C2-462A-8CF8-9BB2A4DC38AE@redhat.com>

Interesting. I had tried this with the latest stable kernel.org kernel 
(as of a month or so ago) and still hit it.

I'll mention that the initial resync on creating the raid1 can be 
interrupted okay; the problem only happens after that completes, and a 
disk is removed and re-added.

Nate



On 02/26/2014 05:21 PM, Brassow Jonathan wrote:
> On Feb 25, 2014, at 4:59 PM, Brassow Jonathan wrote:
>
>> On Feb 25, 2014, at 4:22 PM, Nate Dailey wrote:
>>
>>> Here's what I've done to reproduce this:
>>>
>>> - remove a disk containing one leg of an LVM raid1 mirror
>>> - do enough IO that a lengthy recovery will be required
>>> - insert the removed disk
>>> - let recovery begin, but deactivate the LV before it completes
>>> - activate the LV
>>>
>>> This is the point where the recovery should start back up, but it doesn't. I haven't tried this in a few weeks, but am happy to try it again if it would help.
>> Confirmed (test output below).  I'll get started on this.  This code can be a bit tricky and I've been away from it for a while.  It will take me a bit to re-familiarize myself with it and review your patch.
> I've tested this again with the latest code from upstream (kernel 3.14.0-rc4) and I cannot reproduce the problem there.  I'll see if I can find the last non-working version...
>
>   brassow
>


  reply	other threads:[~2014-02-27  0:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 14:35 [PATCH] dm-raid: check events in super_validate Nate Dailey
2014-02-25  5:30 ` NeilBrown
2014-02-25 22:13   ` Brassow Jonathan
2014-02-25 22:22     ` Nate Dailey
2014-02-25 22:59       ` Brassow Jonathan
2014-02-26 22:21         ` [dm-devel] " Brassow Jonathan
2014-02-27  0:17           ` Nate Dailey [this message]
2014-02-28 20:40             ` Brassow Jonathan
2014-03-01 13:54               ` Brassow Jonathan

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=530E8418.50707@stratus.com \
    --to=nate.dailey@stratus.com \
    --cc=dm-devel@redhat.com \
    --cc=jbrassow@redhat.com \
    --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).