linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Neil Brown <neilb@suse.de>
Cc: Luca Berra <bluca@comedia.it>, linux-raid@vger.kernel.org
Subject: Re: [PATCH] (Re: Questions regarding startup of imsm container)
Date: Wed, 24 Mar 2010 07:49:46 -0700	[thread overview]
Message-ID: <e9c3a7c21003240749y2d8cf545r74b2307ae5dcda0@mail.gmail.com> (raw)
In-Reply-To: <20100324115749.1ac9d6f8@notabene.brown>

On Tue, Mar 23, 2010 at 5:57 PM, Neil Brown <neilb@suse.de> wrote:
> On Tue, 23 Mar 2010 09:04:19 +0100
> Luca Berra <bluca@comedia.it> wrote:
>
>> On Mon, Mar 22, 2010 at 09:56:01PM -0600, Randy Terbush wrote:
>> >Having a go at building a raid5 array using the new imsm support and
>> >having good luck keeping drives in the array, etc. Nice work. I have a
>> >few questions though as I am having some trouble figuring out how to
>> >properly start this container.
>> >
>> ># mdadm --version
>> >mdadm - v3.1.2 - 10th March 2010
>> >
>> ># mdadm -Es
>> >ARRAY metadata=imsm UUID=30223250:76fd248b:50280919:0836b7f0
>> >ARRAY /dev/md/Volume0 container=30223250:76fd248b:50280919:0836b7f0
>> >member=0 UUID=8a4ae452:da1e7832:70ecf895:eb58229c
>> >
>> ># ls -l /dev/md/
>> >total 0
>> >lrwxrwxrwx 1 root root 6 Mar 22 20:54 0 -> ../md0
>> >lrwxrwxrwx 1 root root 8 Mar 22 20:54 127 -> ../md127
>> >lrwxrwxrwx 1 root root 8 Mar 22 20:54 Volume0_0 -> ../md127
>> >
>> >As you can see, the name for the link in /dev/md does not agree with
>> >the name that the Examine is coming up with.
>> please read mdadm.conf manpage, under the section "HOMEHOST"
>>
>> >Is it better to just forgo the ARRAY statements and go with an AUTO +imsm?
>> >
>> >And last, does the concept of a write-intent bitmap make sense on an
>> >imsm container? If so, I get a segv if trying to run mdadm /dev/mdX
>> >-Gb internal on either device.
>>
>> i don't believe it makes sense at all, surely imsm do not support an
>> internal bitmap (no provisioning for it in the metadata)
>>
>> The attached patch completely disables bitmap support for arrays with
>> externally managed metadata.
>
> Thanks for the patch.  However I would prefer to disable bitmap support for
> those metadata formats which report that they don't support it.
> Thus the following patch.
>
> Thanks,
> NeilBrown
>
>
> +               if (!st->ss->add_internal_bitmap) {
[..]
> +               if (st->ss->add_internal_bitmap == NULL) {
[..]
> +               } else if (!st->ss->locate_bitmap) {

The smallest of nits, or maybe just a clarification.  I believe you
have said in the past that you prefer the readability of
positive-logic if statements where possible.

--
Dan
--
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

  parent reply	other threads:[~2010-03-24 14:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23  3:56 Questions regarding startup of imsm container Randy Terbush
2010-03-23  8:04 ` [PATCH] (Re: Questions regarding startup of imsm container) Luca Berra
2010-03-23 12:58   ` Randy Terbush
2010-03-23 14:22     ` Luca Berra
2010-03-23 14:33     ` Randy Terbush
2010-03-23 14:49       ` Randy Terbush
2010-03-23 15:56       ` Luca Berra
2010-03-23 22:41       ` Dan Williams
2010-03-24 21:35         ` Randy Terbush
2010-03-23 23:06   ` [PATCH] " Dan Williams
2010-03-24  0:57   ` Neil Brown
2010-03-24  6:12     ` Luca Berra
2010-03-24 14:49     ` Dan Williams [this message]
2010-03-23 21:01 ` Questions regarding startup of imsm container Dan Williams
2010-03-23 21:41   ` Randy Terbush
2010-03-23 22:16     ` Dan Williams
2010-03-23 23:25       ` Randy Terbush
2010-03-24  0:23         ` Randy Terbush
2010-03-24  4:14           ` Randy Terbush
2010-03-24  5:54           ` Dan Williams

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=e9c3a7c21003240749y2d8cf545r74b2307ae5dcda0@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=bluca@comedia.it \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).