From: Joe Landman <joe.landman@gmail.com>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
linux-raid@vger.kernel.org
Subject: Re: Storage system
Date: Thu, 06 Feb 2014 14:24:35 -0500 [thread overview]
Message-ID: <52F3E173.8020305@gmail.com> (raw)
In-Reply-To: <20140206180909.GA2419@lazy.lzy>
On 02/06/2014 01:09 PM, Piergiorgio Sartor wrote:
> Hi all,
>
> this question is only partially related to Linux MD,
> but since the experts are here, I think it would not
> be a big problem to ask here.
>
> I'm considering a storage system.
> This is based on HDD "rust".
> It should have RAID-6, for protection agaist disk
> failure(s).
> It should have LUKS (or similar), in order to simplify
> HDD disposal (disk that are still somehow readable will
> not need to be wiped out before dumping them).
Can you use the full disk encryption mechanisms? This could
(potentially) save a layer, though the down side is that you don't have
control over it. We've not used it, most of our customers destroying
disks tend to physically destroy them, and not trust the encryption layer.
> It should have LVM, as flexible partition system.
>
> Now, given that the HDD are always the lower layer, the
> others can be combined in any order.
> Six possible combinations, specifically, naming:
>
> H: HDD
> R: RAID
> E: encryption
> L: LVM
>
> We can have:
>
> HREL
> HRLE
> HLRE
> HLER
> HERL
> HELR
If this is a heavily used system, you'll likely want to start with HR
for performance reasons. If you can eliminate the E with FDE as noted,
and if it works well, great. If not, I'd suggest putting that next.
LVM isn't a fast system, so its better not to put it on a fast system.
LUKS can be fast with good CPUs and reasonable controllers/disks.
next prev parent reply other threads:[~2014-02-06 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 18:09 Storage system Piergiorgio Sartor
2014-02-06 19:24 ` Joe Landman [this message]
2014-02-07 8:07 ` David Brown
2014-02-07 14:29 ` Matt Garman
2014-02-07 15:14 ` Roman Mamedov
2014-02-07 15:45 ` Roberto Spadim
2014-02-07 16:11 ` David Brown
2014-02-07 16:25 ` Can Jeuleers
2014-02-07 16:36 ` David Brown
2014-02-08 0:14 ` Chris Murphy
2014-02-07 19:16 ` Robert L Mathews
2014-02-07 23:58 ` 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=52F3E173.8020305@gmail.com \
--to=joe.landman@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.de \
/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).