From: Chris Webb <chris@arachsys.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Assume-clean for md grow
Date: Thu, 26 Feb 2009 14:54:42 +0000 [thread overview]
Message-ID: <20090226145442.GH17577@arachsys.com> (raw)
In-Reply-To: <c5fe66de938d528320cf21d8ca3c7a83.squirrel@neil.brown.name>
NeilBrown <neilb@suse.de> writes:
> Or if you want to be slightly more subtle, remove the
> if (mddev->pers)
> return -EBUSY;
> from resync_start_store. Then before a grow that you want to be
> --assume-clean, write into /sys/block/mdXX/md/resync_start the
> number of sectors in the final raid1 array.
Hi Neil. Thanks for this suggestion: it looks fine for what we're looking to
achieve. Interestingly, this will mean writing a smaller value that shown by
a read from this file for an in-sync array, but will still work?
I'll build a patched kernel and give it a go a little later on.
Best wishes,
Chris.
next prev parent reply other threads:[~2009-02-26 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 14:22 Assume-clean for md grow Chris Webb
2009-02-25 19:34 ` NeilBrown
2009-02-26 14:54 ` Chris Webb [this message]
2009-02-26 15:57 ` Chris Webb
2009-02-26 16:03 ` Chris Webb
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=20090226145442.GH17577@arachsys.com \
--to=chris@arachsys.com \
--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).