From: Jes Sorensen <jes.sorensen@gmail.com>
To: Tomasz Majchrzak <tomasz.majchrzak@intel.com>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/5] Don't combine disks with different sector size in the array
Date: Tue, 9 May 2017 14:18:54 -0400 [thread overview]
Message-ID: <e972c34e-5a78-93d2-06b4-3d870550fb43@gmail.com> (raw)
In-Reply-To: <1494325547-3028-1-git-send-email-tomasz.majchrzak@intel.com>
On 05/09/2017 06:25 AM, Tomasz Majchrzak wrote:
> IMSM doesn't allow to create arrays including drives with different sector
> sizes.
>
> Following patchset blocks all paths to create such configuration:
> * explicit array create
> * array rebuild (spare in the same container, spare moved across containers)
> * array grow
>
> Alexey Obitotskiy (5):
> imsm: allow drives in a container regardless of sector size
> imsm: allocate buffer to support maximum sector size
> imsm: don't allow disks with different sector size in one array
> Allow more spare selection criteria
> Add sector size as spare selection criterion
>
> Incremental.c | 18 ++++++++-----
> Monitor.c | 38 ++++++++++++++++----------
> mdadm.h | 19 +++++++++----
> super-intel.c | 86 ++++++++++++++++++++++++++++++++++++++++-------------------
> util.c | 37 ++++++++++++++++++++++---
> 5 files changed, 140 insertions(+), 58 deletions(-)
>
Applied!
Thanks,
Jes
prev parent reply other threads:[~2017-05-09 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 10:25 [PATCH 0/5] Don't combine disks with different sector size in the array Tomasz Majchrzak
2017-05-09 10:25 ` [PATCH 1/5] imsm: allow drives in a container regardless of sector size Tomasz Majchrzak
2017-05-09 10:25 ` [PATCH 2/5] imsm: allocate buffer to support maximum " Tomasz Majchrzak
2017-05-09 10:25 ` [PATCH 3/5] imsm: don't allow disks with different sector size in one array Tomasz Majchrzak
2017-05-09 10:25 ` [PATCH 4/5] Allow more spare selection criteria Tomasz Majchrzak
2017-05-09 10:25 ` [PATCH 5/5] Add sector size as spare selection criterion Tomasz Majchrzak
2017-05-09 18:18 ` Jes Sorensen [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=e972c34e-5a78-93d2-06b4-3d870550fb43@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=tomasz.majchrzak@intel.com \
/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).