From: Roman Mamedov <roman@rm.pp.ru>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 and crashes (reporting back re. --bitmap)
Date: Fri, 11 Jun 2010 03:41:08 +0600 [thread overview]
Message-ID: <20100611034108.6a2cdbc4@natsu> (raw)
In-Reply-To: <4C11578B.8010202@meetinghouse.net>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
On Thu, 10 Jun 2010 17:22:19 -0400
Miles Fidelman <mfidelman@meetinghouse.net> wrote:
> > Do you currently have a write intent bitmap in the array? I think it can
> > reduce the need for recovery by an order of magnitude in some cases. Check
> > man mdadm for --bitmap if you don't use it yet.
> >
> Just went through the process of turning it on for all my arrays.
> Incredibly painless and quick. Now I get to wait and see if it helps
> the next time I have a crash/reboot event.
I assume you went with "internal" bitmap, in which case if you notice that
write speed on the arrays became significantly lower, the first thing you
should look at is increasing the --bitmap-chunk size (I use 131072).
It is possible to use an external bitmap on an independent device (which has
almost zero performance impact), but in this case it could be non-trivial to
100% ensure that such a device is mounted and accessible at the moment during
boot-up when md arrays are being started, especially if one of those arrays
also hosts the root FS.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-10 21:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 18:02 RAID6 and crashes Miles Fidelman
2010-06-10 18:57 ` Roman Mamedov
2010-06-10 21:22 ` RAID6 and crashes (reporting back re. --bitmap) Miles Fidelman
2010-06-10 21:41 ` Roman Mamedov [this message]
2010-06-10 22:40 ` Miles Fidelman
2010-06-11 2:51 ` Roman Mamedov
2010-06-11 4:31 ` Graham Mitchell
2010-06-11 4:41 ` Roman Mamedov
2010-06-11 12:13 ` Graham Mitchell
2010-06-11 4:42 ` Miles Fidelman
2010-06-11 4:50 ` Neil Brown
2010-06-13 14:28 ` Bernd Schubert
2010-06-13 23:05 ` Neil Brown
2010-06-14 9:01 ` Bernd Schubert
2010-06-14 9:14 ` Roman Mamedov
2010-06-14 9:47 ` Neil Brown
2010-06-14 11:53 ` Roman Mamedov
2010-06-14 21:24 ` Neil Brown
2010-06-11 4:46 ` Miles Fidelman
2010-06-11 4:55 ` Roman Mamedov
2010-06-11 20:26 ` Miles Fidelman
2010-06-11 5:08 ` Neil Brown
2010-06-11 11:10 ` John Hendrikx
2010-06-11 11:50 ` Roman Mamedov
2010-06-11 12:29 ` Graham Mitchell
2010-06-11 12:25 ` Graham Mitchell
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=20100611034108.6a2cdbc4@natsu \
--to=roman@rm.pp.ru \
--cc=linux-raid@vger.kernel.org \
--cc=mfidelman@meetinghouse.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.