linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Neubauer, Wojciech" <Wojciech.Neubauer@intel.com>,
	Doug Ledford <dledford@redhat.com>,
	Ed Ciechanowski <ed.ciechanowski@intel.com>,
	"Hawrylewicz Czarnowski,
	Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@intel.com>,
	marcin.labun@intel.com, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes
Date: Mon, 31 May 2010 11:37:10 +1000	[thread overview]
Message-ID: <20100531113710.29e12d97@notabene.brown> (raw)
In-Reply-To: <1274921452.17973.253.camel@dwillia2-linux>

On Wed, 26 May 2010 17:50:52 -0700
Dan Williams <dan.j.williams@intel.com> wrote:

> Hi Neil,
> 
> A collection of updates that have been separated onto individual topic
> branches.  I provide a url, summary, and full diff for each topic if you
> want to do piecemeal pulls, otherwise the merged set is available here:
> 
> 	git://github.com/djbw/mdadm.git master
> 
> Dan Williams (10):
>       mdmon: fix missing open of md/<dev>/recovery_start
>       mdmon: periodically checkpoint recovery

I don't understand why you write 'idle' to 'sync_action' here. 
It should not be needed.
Shouldn't we just be listening for events on sync_completed, and write
them to the metadata??

>       imsm: dump each disk's view of the slot state
>       Kill subarray

I assume that this is only allowed on an idle container because the 
volume index number of subsequent volumes will change, and as that is used in
the uuid the uuid will change, and that is bad.
1/ Can you leave a 'place-holder' empty volume in the list, that a subsequent
   create can use?
2/ As ddf doesn't suffer from this issue, the test for 'active volume that 
   will get a new uuid' should be in the super-intel code.  And it should
   be exactly that test - if earlier volumes are active, that should not be a
   problem.
   Maybe a new method "safe_to_delete_volume".... or something.

Also:  -ENODOC.

>       Rename subarray

Rename will change the uuid of the renamed array, but not the uuid of
anything else, so it should be allowed if just the volume is inactive.

Also it would be nicer if you factored out open_subarray in the previous
patch, but that isn't a big issue (I would still accept if that was the only
issue).


>       Incremental: honor an 'enough' flag from external handlers
>       Revert "Incremental: honor --no-degraded to delay assembly"
>       Merge branch 'subarray' into for-neil
>       imsm: robustify recovery-start detection

"robistify" !! Is that a neologism ??


I've merged and pushed out the other bits which all seem OK.

Thanks,
NeilBrown


  reply	other threads:[~2010-05-31  1:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27  0:50 [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes Dan Williams
2010-05-31  1:37 ` Neil Brown [this message]
2010-06-11  6:42   ` Dan Williams
2010-06-16  6:33     ` Neil Brown
2010-07-02  0:56       ` Dan Williams
2010-07-06  4:50         ` Neil Brown
2010-07-06 19:51           ` fixes for 3.1.3 (was: Re: [mdadm GIT PULL] rebuild checkpoints...) Dan Williams
2010-07-21 18:04             ` Dan Williams
2010-07-22  7:47               ` Neil Brown
2010-07-06 21:43           ` [mdadm GIT PULL] rebuild checkpoints, incremental assembly, volume delete/rename, and fixes Doug Ledford
2010-07-06 22:17             ` Neil Brown
2010-07-07 14:03               ` Doug Ledford
2010-07-08  7:50                 ` Neil Brown

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=20100531113710.29e12d97@notabene.brown \
    --to=neilb@suse.de \
    --cc=Wojciech.Neubauer@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dledford@redhat.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=marcin.labun@intel.com \
    --cc=przemyslaw.hawrylewicz.czarnowski@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).