public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Cc: linux-raid@vger.kernel.org, devon@sigmalabsinc.com
Subject: Re: [PATCH] Assemble: start dirty and degraded array.
Date: Tue, 27 Jul 2021 17:36:00 -0400	[thread overview]
Message-ID: <a08029cf-6e87-995e-cb6c-37169f1c4bd5@trained-monkey.org> (raw)
In-Reply-To: <20210721154754.31872-1-mariusz.tkaczyk@linux.intel.com>

On 7/21/21 11:47 AM, Mariusz Tkaczyk wrote:
> The case when array is already degraded has been omitted
> by commit 7b99edab2834 ("Assemble.c: respect force flag.").
> Appropriative support has been added now.
> 
> Handlers for "run" and "force" have been divided into independent
> routines. Especially force has to be as meaningless as possible.
> It respects following rules:
>     - user agrees to start array as degraded (by --run) or is already
>       degraded
>     - raid456 module is in use
>     - some drives are missing (to limit potential abuses)
> 
> It doesn't allow to skip resync on dirty, but not degraded array.
> 
> This patch cleans up message generation for external array and makes it
> consistent. Following code could be reused also for native.
> 
> In current implementation assemble_container_content is called once, in
> both Incremental or Assembly mode. Thus makes that partial assembly is
> not likely to happen. It is possible, but requires user input.
> Partial assembly during reshape fails (sysfs_set_array
> error - not yet investigated). For now I put FIXME to mark current
> logic as known to be buggy because preexist_cnt contains both exp_cnt
> and new_cnt which may produce an incorrect message.
> 
> Check for new disks and runstop is unnecessary, so has been removed.
> This allows to print assemble status in every case, even if nothing new
> happens.
> 
> Reported-by: Devon Beets <devon@sigmalabsinc.com>
> Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> ---
>  Assemble.c    | 176 +++++++++++++++++++++++++++++---------------------
>  mdadm.8.in    |   3 +-
>  super-intel.c |   4 --
>  3 files changed, 103 insertions(+), 80 deletions(-)
> 

Applied!

Thanks,
Jes


      reply	other threads:[~2021-07-27 21:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 15:47 [PATCH] Assemble: start dirty and degraded array Mariusz Tkaczyk
2021-07-27 21:36 ` 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=a08029cf-6e87-995e-cb6c-37169f1c4bd5@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=devon@sigmalabsinc.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mariusz.tkaczyk@linux.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