All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominic Raferd <dominic@timedicer.co.uk>
To: linux-raid@vger.kernel.org
Subject: SSD + Rust as raid1
Date: Thu, 30 May 2013 22:23:59 +0100	[thread overview]
Message-ID: <51A7C36F.4030605@timedicer.co.uk> (raw)

I am wanting to (re)set up my raid1 array with 1 SSD partition 
(/dev/sda2) and 1 'rust' drive partition (/dev/sdb1) , both 240GB. SSD 
will also have a very small ext2 partition mounted as /mnt/sda1 (to hold 
the write-intent bitmap file).

To get the full speed of the SSD for reads and to maximise speed for 
writes I plan to use these settings:

mdadm -C /dev/md0 --level=raid1 -n 2 /dev/sda2 --write-mostly 
--write-behind=16384 --bitmap=/mnt/sda1/write-intent-bitmap.file 
--bitmap-chunk=256M dev/sdb1

Will this work and be optimal? I am not too bothered about the 
write-intent bitmap file but it is not optional I think, hence I set a 
large chunk size, could or should it be even larger (or smaller)? 
Similarly I have tried to set a high write-behind to speed up writes as 
much as possible - is 16384 the maximum allowed?

My system has mdadm 3.2.3 and kernel 3.2.26.

Any suggestions gratefully received.

Dominic

             reply	other threads:[~2013-05-30 21:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 21:23 Dominic Raferd [this message]
2013-05-31  0:22 ` SSD + Rust as raid1 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
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=51A7C36F.4030605@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.