From: keld@keldix.com
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Doug Ledford <dledford@redhat.com>,
Stan Hoeppner <stan@hardwarefreak.com>,
Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RFC swap over raid1
Date: Fri, 2 Aug 2013 20:26:40 +0200 [thread overview]
Message-ID: <20130802182640.GA31414@www5.open-std.org> (raw)
In-Reply-To: <CAH3kUhH840NmKbzOitQCZoPTfO3Oo+RqeCVvb3T_m3uRhKM1aA@mail.gmail.com>
On Fri, Aug 02, 2013 at 02:29:50PM -0300, Roberto Spadim wrote:
> nice, well, considering everything...
>
> 1)partitions + raid1 is prefered for read speed and security
> 2)fileswap only if i can't add partitions
> 3)only use swap over single drive if don't have two devices (in this
> case use raid1)
> 4)there's no badblock layer in linux, each layer / filesystem must
> implement it by yourself
>
> that's all right?
I would use raid10,far for its faster read vs raid1.
There is badblock handling in the raid layer.
Best regards
keld
next prev parent reply other threads:[~2013-08-02 18:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 22:11 RFC swap over raid1 Roberto Spadim
2013-08-01 23:04 ` Doug Ledford
2013-08-02 2:01 ` Roberto Spadim
2013-08-02 7:46 ` Stan Hoeppner
2013-08-02 14:21 ` Roberto Spadim
2013-08-02 15:40 ` Doug Ledford
2013-08-02 15:59 ` Roberto Spadim
2013-08-02 16:35 ` Doug Ledford
2013-08-02 16:40 ` Roberto Spadim
2013-08-02 16:50 ` Doug Ledford
2013-08-02 17:29 ` Roberto Spadim
2013-08-02 17:35 ` Doug Ledford
2013-08-02 17:38 ` Roberto Spadim
2013-08-02 18:26 ` keld [this message]
2013-08-02 18:39 ` Roberto Spadim
2013-08-02 21:31 ` Keld Jørn Simonsen
2013-08-02 15:21 ` Doug Ledford
2013-08-02 1:59 ` Brad Campbell
2013-08-02 2:02 ` Roberto Spadim
2013-08-02 2:18 ` Brad Campbell
2013-08-02 2:21 ` Roberto Spadim
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=20130802182640.GA31414@www5.open-std.org \
--to=keld@keldix.com \
--cc=dledford@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
--cc=stan@hardwarefreak.com \
/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.