From: Steven Haigh <netwiz@crc.id.au>
To: Richard Grundy <richguk@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm raid5 with lvm: advantages?
Date: Wed, 12 Jan 2011 01:10:03 +1100 [thread overview]
Message-ID: <4D2C64BB.6070803@crc.id.au> (raw)
In-Reply-To: <AANLkTineOZXNQaGoF_WDnzHbzvCq0=Fi+kw=TseV+agQ@mail.gmail.com>
On 12/01/2011 1:06 AM, Richard Grundy wrote:
> 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.
I used lvm over RAID5 on my latest server. It runs the Xen Hypervisor to
do virtualisation. It was the first project that I have *ever* used lvm
on. I have to say, I'm quite impressed. I have a volume group that takes
up the entire RAID5, then split that into logical volumes for each VM.
I guess the bottom line here is what you are using it for. If its one
massive file dumping ground, then lvm probably won't get you any extra
features. If you plan to have more things later on than a single
filesystem, then it might be an advantage to put lvm on there now.
--
Steven Haigh
Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
next prev parent reply other threads:[~2011-01-11 14:10 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 [this message]
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
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=4D2C64BB.6070803@crc.id.au \
--to=netwiz@crc.id.au \
--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 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.