From: Eli Stair <estair@ilm.com>
To: linux-raid mailing list <linux-raid@vger.kernel.org>
Subject: Setting write-intent bitmap during array resync/create?
Date: Tue, 10 Oct 2006 12:31:17 -0700 [thread overview]
Message-ID: <452BF505.9020608@ilm.com> (raw)
I gather this isn't currently possible, but I wonder if it's feasible to
make it so? This works fine once the array is marked 'clean', and I
imagine it's simpler to just disallow the bitmap creation until it's in
that state. Would it be possible to allow creation of the bitmap by
queueing the action until the array is done rebuilding?
The reason for this concern is I've got a plethora of systems that are
set for auto-deployment; that is they can be booted into a mode where
they will have no existing array and will create it from scratch. I
will be using the write-intent bitmap, but in the present state I have
to set a job to monitor the array state and manually issue the create
command when it is finished building.
It seems a good candidate for being able to specify this option at array
creation time along with all other options.
Just a suggestion/feature request.
Cheers,
/eli
// WI Bitmap creation attempt:
[root@gtmp08 /]# mdadm /dev/md0 -Gb internal
mdadm: failed to set internal bitmap.
md: couldn't update array info. -16
// MD state:
Personalities : [raid10]
md0 : active raid10 dm-9[13] dm-8[12] dm-7[11] dm-6[10] dm-5[9] dm-4[8]
dm-3[7] dm-2[6] dm-13[5] dm-11[4] dm-12[3] dm-10[2] dm-1[1] dm-0[0]
1003620352 blocks super 1.2 512K chunks 2 offset-copies [14/14]
[UUUUUUUUUUUUUU]
[==>..................] resync = 12.2% (123160576/1003620352)
finish=225.5min speed=65050K/sec
unused devices: <none>
next reply other threads:[~2006-10-10 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 19:31 Eli Stair [this message]
2006-10-11 5:14 ` Setting write-intent bitmap during array resync/create? dean gaudet
2006-10-11 20:11 ` Eli Stair
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=452BF505.9020608@ilm.com \
--to=estair@ilm.com \
--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 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).