From: Zdenek Kaspar <zkaspar82@gmail.com>
To: Richard Grundy <richguk@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm raid5 with lvm: advantages?
Date: Tue, 11 Jan 2011 19:36:30 +0100 [thread overview]
Message-ID: <4D2CA32E.3030303@gmail.com> (raw)
In-Reply-To: <AANLkTineOZXNQaGoF_WDnzHbzvCq0=Fi+kw=TseV+agQ@mail.gmail.com>
Dne 11.1.2011 15:06, Richard Grundy napsal(a):
> Hi,
>
> I'm building a new RAID5 array (of 5 1.5 TB drives) with mdadm and
> would like to know the benefits of creating an LVM on top of this are
> instead of just creating the filesystem on the md directly. I've never
> had a problem growing the array and then resizing the filesystem
> before and wondered if in this situation the only gain would be lvm
> snapshot stuff? I'm planning to use ext4 for this array, if that makes
> any difference.
>
> Thanks in advanced,
>
> Rich
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Really depends on your needs..
It makes sense to use LVM for virtualization and iSCSI to get rid of big
file images (unwanted fs overhead/fragmentation). But yes, in some use
cases this is OK.
If you don't need snapshots or whatever LVM feature, then go the
simplest way - no LVM.
HTH, Z.
next prev parent reply other threads:[~2011-01-11 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 14:06 mdadm raid5 with lvm: advantages? Richard Grundy
2011-01-11 14:10 ` Steven Haigh
2011-01-11 14:13 ` Richard Grundy
2011-01-11 14:16 ` Jan Kasprzak
2011-01-11 16:30 ` CoolCold
2011-01-11 18:36 ` Zdenek Kaspar [this message]
2011-01-11 18:40 ` Roberto Spadim
2011-01-11 18:49 ` Roman Mamedov
2011-01-11 18:58 ` Roy Keene
2011-01-11 19:11 ` Zdenek Kaspar
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=4D2CA32E.3030303@gmail.com \
--to=zkaspar82@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=richguk@gmail.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 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).