linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: What happens with array when external write-intent bitmap fails?
Date: Mon, 22 Sep 2014 13:37:13 +1000	[thread overview]
Message-ID: <20140922133713.53a1ff27@notabene.brown> (raw)
In-Reply-To: <CAA91j0X2WSyF_QuZdoWWNgDCZV7TKJbhQmq_vOrygqzkg3yK8g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Tue, 16 Sep 2014 17:42:13 +0400 Andrei Borzenkov <arvidjaar@gmail.com>
wrote:

> Theoretically write-intent is optional, so if it fails it would be
> possible to simply discard it and continue. But I have seen statement
> that if external write-intent bitmap file is not available at time of
> assembly, starting of array fails.
> 
> Thank you for clarification.

What exactly did you want clarified?

I suggest the best thing to do is to use "losetup" to create some loop-back
devices.  Then use mdadm to create an array using those devices.
Then simulate the failure mode that you are concerned about and see what
happens.

If you find that the documentation does not agree with reality, please
consider posting details.

Thanks,
NeilBrown

> 
> -andrei
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2014-09-22  3:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 13:42 What happens with array when external write-intent bitmap fails? Andrei Borzenkov
2014-09-22  3:37 ` NeilBrown [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=20140922133713.53a1ff27@notabene.brown \
    --to=neilb@suse.de \
    --cc=arvidjaar@gmail.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).