From: Phil Turmel <philip@turmel.org>
To: ian_bruce@mail.ru, linux-raid@vger.kernel.org
Subject: Re: [BUG] non-metadata arrays cannot use more than 27 component devices
Date: Fri, 24 Feb 2017 10:20:52 -0500 [thread overview]
Message-ID: <41ea334c-ae1c-dac6-e1a1-480d3700a588@turmel.org> (raw)
In-Reply-To: <20170224040816.41f2f372.ian_bruce@mail.ru>
On 02/24/2017 07:08 AM, ian_bruce@mail.ru wrote:
> When assembling non-metadata arrays ("mdadm --build"), the in-kernel
> superblock apparently defaults to the MD-RAID v0.90 type. This
> imposes a maximum of 27 component block devices, presumably as well
> as limits on device size.
>
> mdadm does not allow you to override this default, by specifying the
> v1.2 superblock. It is not clear whether mdadm tells the kernel to
> use the v0.90 superblock, or the kernel assumes this by itself. One
> or other of them should be fixed; there does not appear to be any
> reason why the v1.2 superblock should not be the default in this
> case.
>
> details are here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855871
>
> This problem is easy to reproduce, even with simple hardware. You
> can use /dev/loop devices as the array components, as explained in
> the link.
Considering the existence of --build is strictly to support arrays that
predate MD raid, it seems a bit of a stretch to claim this as a bug
instead of a feature request.
When you implement this feature, you might want to consider extending
modern MD raid's support for external metadata to use RAM and then
you could do whatever you please with the array events.
See "man mdmon" for a summary of external metadata events.
Phil
next prev parent reply other threads:[~2017-02-24 15:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 12:08 [BUG] non-metadata arrays cannot use more than 27 component devices ian_bruce
2017-02-24 15:20 ` Phil Turmel [this message]
2017-02-24 16:40 ` ian_bruce
2017-02-24 20:46 ` Phil Turmel
2017-02-25 20:05 ` Anthony Youngman
2017-02-25 22:00 ` Phil Turmel
2017-02-25 23:30 ` Wols Lists
2017-02-25 23:41 ` Phil Turmel
2017-02-25 23:55 ` Wols Lists
2017-02-26 0:07 ` Phil Turmel
2017-03-01 15:02 ` Wols Lists
2017-03-01 17:23 ` Phil Turmel
2017-03-01 18:13 ` Phil Turmel
2017-03-01 19:50 ` Anthony Youngman
2017-03-01 22:20 ` Phil Turmel
2017-02-27 5:55 ` NeilBrown
2017-02-28 10:25 ` ian_bruce
2017-02-28 20:29 ` NeilBrown
2017-03-01 13:05 ` ian_bruce
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=41ea334c-ae1c-dac6-e1a1-480d3700a588@turmel.org \
--to=philip@turmel.org \
--cc=ian_bruce@mail.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.