linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: RAID5 created by 8 disks works with xfs
Date: Sun, 01 Apr 2012 12:33:18 +0200	[thread overview]
Message-ID: <jl9ate$2me$1@dough.gmane.org> (raw)
In-Reply-To: <4F77EA55.6090004@hardwarefreak.com>

On 01/04/12 07:40, Stan Hoeppner wrote:
> On 4/1/2012 12:12 AM, daobang wang wrote:
>> Thank you very much!
>> I got it, so we can remove the Volume Group and Logical Volume to save resource.
>> And i will try RAID5 with 16 disks to write 96 total streams again.
>
> Why do you keep insisting on RAID5?!?!  It is not suitable for your
> workload.  It sucks Monday through Saturday and twice on Sunday for this
> workload.
>

My thoughts on this setup are that RAID5 (or RAID6) is a poor choice - 
it can quickly cause a mess for streaming writes.  Even if the streams 
themselves can mostly end up as full stripe writes, odd writes such as 
the end of a file, metadata writes, log data writes, etc., will mean 
read-modify-write operations that will cripple the write performance for 
the rest of the operations.

And if a disk fails so that you are running degraded, it will be hopeless.

Either drop the redundancy requirement entirely (maybe by making sure 
other backups are in order), or double the spindles and use RAID1 / RAID10.


For an application like this, it would probably make sense to put the 
xfs log (and the mdraid bitmap file, if you are using one) on a separate 
disk - perhaps a small SSD.


  parent reply	other threads:[~2012-04-01 10:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-31  1:22 RAID5 created by 8 disks works with xfs daobang wang
2012-03-31  7:59 ` Mathias Burén
2012-03-31 20:09   ` Stan Hoeppner
2012-04-01  1:16     ` daobang wang
2012-04-01  2:05       ` daobang wang
2012-04-01  5:13         ` Stan Hoeppner
2012-04-01  3:51       ` Stan Hoeppner
2012-04-01  5:12         ` daobang wang
2012-04-01  5:40           ` Stan Hoeppner
2012-04-01  5:59             ` daobang wang
2012-04-01  6:20               ` daobang wang
2012-04-01  7:08                 ` Marcus Sorensen
2012-04-02  3:47                   ` Stan Hoeppner
2012-04-05  0:48                     ` daobang wang
     [not found]                       ` <CACwgYDOtCoVF-p+KKqPYxHhA4vWF78Ueecx9hcVWLoyxFWzV9Q@mail.gmail.com>
2012-04-05 21:01                         ` Stan Hoeppner
2012-04-06  0:25                           ` daobang wang
2012-04-06  2:33                             ` daobang wang
2012-04-06  6:00                               ` Jack Wang
2012-04-06  6:45                                 ` daobang wang
2012-04-06  6:49                                   ` daobang wang
2012-04-06  8:18                                     ` Stan Hoeppner
2012-04-06  8:45                                       ` daobang wang
2012-04-06 11:12                                         ` Stan Hoeppner
2012-04-18  2:23                                           ` daobang wang
2012-04-02  3:12                 ` Stan Hoeppner
2012-04-01 10:33             ` David Brown [this message]
2012-04-01 12:28               ` John Robinson
2012-04-02  6:59                 ` David Brown
     [not found]                 ` <CA+res+QkLi7sxZrD-XOcbR47CeJ5gADf7P6pa1w1oMf8CKSB4g@mail.gmail.com>
2012-04-02  8:01                   ` John Robinson
2012-04-02 10:01                     ` Jack Wang
2012-04-02 10:28                       ` John Robinson
2012-04-02 20:41                         ` Stan Hoeppner
2012-04-02  5:43               ` Stan Hoeppner
2012-04-02  7:04                 ` David Brown
2012-04-02 20:21                   ` Stan Hoeppner
2012-04-01  4:52       ` Stan Hoeppner
2012-04-01  8:06         ` John Robinson

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='jl9ate$2me$1@dough.gmane.org' \
    --to=david.brown@hesbynett.no \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).