From: Erkki Seppala <flux-btrfs@inside.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to stress test raid6 on 122 disk array
Date: Fri, 05 Aug 2016 13:15:17 +0300 [thread overview]
Message-ID: <m49k2fvmsi2.fsf@coffee.modeemi.fi> (raw)
In-Reply-To: CAGQ70YfvcujVWs-Hr-jLS5DED3ti5XK=fVhx6M8K7c85UVYDhA@mail.gmail.com
Martin <rc6encrypted@gmail.com> writes:
> The smallest disk of the 122 is 500GB. Is it possible to have btrfs
> see each disk as only e.g. 10GB? That way I can corrupt and resilver
> more disks over a month.
Well, at least you can easily partition the devices for that to happen.
However, I would also suggest that would it be more useful use of the
resource to run many arrays in parallel? Ie. one 6-device raid6, one
20-device raid6, and then perhaps use the rest of the devices for a very
large btrfs filesystem? Or if you have been using partitioning the large
btrfs volume can also be composed of all the 122 devices; in fact you
could even run multiple 122-device raid6s and use different kind of
testing on each. For performance testing you might only excert one of
the file systems at a time, though.
--
_____________________________________________________________________
/ __// /__ ____ __ http://www.modeemi.fi/~flux/\ \
/ /_ / // // /\ \/ / \ /
/_/ /_/ \___/ /_/\_\@modeemi.fi \/
next prev parent reply other threads:[~2016-08-05 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 17:43 How to stress test raid6 on 122 disk array Martin
2016-08-04 19:05 ` Austin S. Hemmelgarn
2016-08-04 20:01 ` Chris Murphy
2016-08-04 20:51 ` Martin
2016-08-04 21:12 ` Chris Murphy
2016-08-04 22:19 ` Martin
2016-08-05 10:15 ` Erkki Seppala [this message]
2016-08-15 12:19 ` Martin
2016-08-15 12:38 ` Austin S. Hemmelgarn
2016-08-15 13:39 ` Martin
2016-08-15 13:47 ` Austin S. Hemmelgarn
2016-08-05 11:39 ` Austin S. Hemmelgarn
2016-08-15 12:19 ` Martin
2016-08-15 12:44 ` Austin S. Hemmelgarn
2016-08-15 13:38 ` Martin
2016-08-15 13:41 ` Austin S. Hemmelgarn
2016-08-15 13:43 ` Chris Murphy
2016-08-15 13:40 ` Chris Murphy
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=m49k2fvmsi2.fsf@coffee.modeemi.fi \
--to=flux-btrfs@inside.org \
--cc=linux-btrfs@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.