From: "Peter Sangas" <pete@wnsdev.com>
To: 'Phil Turmel' <philip@turmel.org>,
'Ramon Hofer' <ramonhofer@bluewin.ch>,
linux-raid@vger.kernel.org
Subject: RE: "bitmap" line in /proc/mdstat
Date: Fri, 14 Oct 2016 09:08:25 -0700 [thread overview]
Message-ID: <003401d22635$32b7bc70$98273550$@wnsdev.com> (raw)
In-Reply-To: <8922e2e1-b612-fa32-6932-9f4158f52fe6@turmel.org>
Can you quantify the performance decrease and if rebuild time is not as important as performance how does one remove the bitmap?
Thank you,
Peter
-----Original Message-----
From: Phil Turmel [mailto:philip@turmel.org]
Sent: Friday, October 14, 2016 4:53 AM
To: Ramon Hofer; linux-raid@vger.kernel.org
Subject: Re: "bitmap" line in /proc/mdstat
On 10/14/2016 06:06 AM, Ramon Hofer wrote:
> From what I was reading [1,2] it is useful for faster rebuilds.
> But why is it not present for md[1234] as I used the same command to
> create these RAIDs?
> Is it only possible for the last of the linear devices, or is it only
> used for almost empty devices, or was the bitmap introduced in a
> recent update?
Bitmaps have been available for a long time, but including them on a new array by default is recent. They are most useful if a device is unexpectedly disconnected but otherwise OK. mdadm --re-add will allow that device to rejoin the array and only the missing data (tracked by the bitmap) will have to be written to sync it up.
> I wonder if I should and could add a bitmap for the other devices as well?
There is a performance hit, so it should be considered on a case by case basis.
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-10-14 16:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 10:06 "bitmap" line in /proc/mdstat Ramon Hofer
2016-10-14 11:53 ` Phil Turmel
2016-10-14 12:32 ` Ramon Hofer
2016-10-14 13:59 ` Ramon Hofer
2016-10-14 14:10 ` Andreas Klauer
2016-10-14 14:23 ` Ramon Hofer
2016-10-14 16:08 ` Peter Sangas [this message]
2016-10-14 16:29 ` Ramon Hofer
2016-10-14 17:32 ` Peter Sangas
2016-10-14 17:38 ` Ramon Hofer
2016-10-14 17:43 ` Andreas Klauer
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='003401d22635$32b7bc70$98273550$@wnsdev.com' \
--to=pete@wnsdev.com \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--cc=ramonhofer@bluewin.ch \
/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