From: "Peter Sangas" <pete@wnsdev.com>
To: 'Ramon Hofer' <ramonhofer@bluewin.ch>, linux-raid@vger.kernel.org
Subject: RE: "bitmap" line in /proc/mdstat
Date: Fri, 14 Oct 2016 10:32:47 -0700 [thread overview]
Message-ID: <005501d22640$fc4d6a20$f4e83e60$@wnsdev.com> (raw)
In-Reply-To: <580107FA.40901@bluewin.ch>
Thanks Ramon.
Do you know why some of your mds were created with bitmaps and others were not? When I installed Ubuntu 16.04 and used the installer to create a RAID1 some of the mds had bitmaps and some did not.
Thanks,
Pete
-----Original Message-----
From: Ramon Hofer [mailto:ramonhofer@bluewin.ch]
Sent: Friday, October 14, 2016 9:30 AM
To: Peter Sangas; linux-raid@vger.kernel.org
Subject: Re: "bitmap" line in /proc/mdstat
On 14/10/16 18:08, Peter Sangas wrote:
> Can you quantify the performance decrease and if rebuild time is not as important as performance how does one remove the bitmap?
From the Linux RAID wiki:
"Some limited measurements I have done suggest up to 10% slowdown, though usually less. Possibly some tuning can make it much better." [1]
[1]
https://raid.wiki.kernel.org/index.php/Write-intent_bitmap#How_Bitmaps_Work_by_Q.26A
Regards,
Ramon
--
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 17:32 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
2016-10-14 16:29 ` Ramon Hofer
2016-10-14 17:32 ` Peter Sangas [this message]
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='005501d22640$fc4d6a20$f4e83e60$@wnsdev.com' \
--to=pete@wnsdev.com \
--cc=linux-raid@vger.kernel.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