From: Dominic Raferd <dominic@timedicer.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: SSD + Rust as raid1
Date: Fri, 31 May 2013 09:52:49 +0100 [thread overview]
Message-ID: <51A864E1.9070903@timedicer.co.uk> (raw)
In-Reply-To: <20130531135434.5b6bdddb@natsu>
On 31/05/2013 08:54, Roman Mamedov wrote:
> On Fri, 31 May 2013 08:47:00 +0100
> Dominic Raferd <dominic@timedicer.co.uk> wrote:
>
>> This is my idea too (see my OP), but I am concerned about optimisation
>> (--write-behind, --bitmap and --bitmap-chunk settings) especially for
>> writes.
>> --write-behind=16384
> I think this will not work, you will have to use 16383.
Oh, OK, so 16383 is the maximum then?
>> --bitmap=/mnt/sda1/write-intent-bitmap.file
> Save yourself lots of maintenance headache, just use --bitmap=internal
>
>> --bitmap-chunk=256M
> Looks OK.
>
Thanks Roman, but the problem with using --bitmap=internal is that, as
Neil Brown posted here on another topic a while ago, this requires a
synch write to both devices, and the use-case for which write-behind was
developed involved an external bitmap. Hence my plan to use external
bitmap file on a fast (SSD-based) separate partition - minimises any
slow-down caused by having to maintain the write-intent bitmap file.
next prev parent reply other threads:[~2013-05-31 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 21:23 SSD + Rust as raid1 Dominic Raferd
2013-05-31 0:22 ` Mathias Burén
2013-05-31 7:02 ` Dominic Raferd
2013-05-31 7:30 ` Roman Mamedov
2013-05-31 7:47 ` Dominic Raferd
2013-05-31 7:54 ` Roman Mamedov
2013-05-31 8:52 ` Dominic Raferd [this message]
2013-06-04 8:13 ` Dominic Raferd
2013-06-07 22:23 ` Bill Davidsen
2013-06-08 10:22 ` Roman Mamedov
2013-06-08 17:11 ` Bill Davidsen
2013-06-08 21:58 ` Roberto Spadim
2013-06-10 8:57 ` Dominic Raferd
2013-06-01 0:25 ` Stan Hoeppner
2013-06-01 1:19 ` Keith Keller
2013-06-01 4:37 ` Stan Hoeppner
2013-06-07 22:16 ` Bill Davidsen
2013-06-01 1:30 ` Sam Bingner
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=51A864E1.9070903@timedicer.co.uk \
--to=dominic@timedicer.co.uk \
--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 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.