From: Roy Keene <linux-raid@rkeene.org>
To: Roman Mamedov <rm@romanrm.ru>
Cc: Zdenek Kaspar <zkaspar82@gmail.com>,
Richard Grundy <richguk@gmail.com>,
linux-raid@vger.kernel.org
Subject: Re: mdadm raid5 with lvm: advantages?
Date: Tue, 11 Jan 2011 12:58:02 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.1101111254530.1805@claw.oc9.org> (raw)
In-Reply-To: <20110111234945.7c601067@natsu>
Roman,
LVM supports both sparse LVs (--virtualsize) and defragmentation
(though as you say it's not currently easy -- I started writing a script
to handle it but it's not a big enough problem that I've ever actually
wanted to use the script, still a general purpose "lvdefrag" could be
written).
Thanks,
Roy Keene
On Tue, 11 Jan 2011, Roman Mamedov wrote:
> On Tue, 11 Jan 2011 19:36:30 +0100
> Zdenek Kaspar <zkaspar82@gmail.com> wrote:
>
>> 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.
>
> Since you mentioned fragmentation - there are ways to both make sparse file
> images, and to defragment them when needed (on some filesystems like XFS and
> btrfs). But when using LVM instead of file images, the user has neither: LVM
> can't have sparse LVs, and it can't (easily) defragment an LV that is
> fragmented over one or several PVs. Or am I missing something here?
>
> --
> With respect,
> Roman
>
next prev parent reply other threads:[~2011-01-11 18:58 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
2011-01-11 18:40 ` Roberto Spadim
2011-01-11 18:49 ` Roman Mamedov
2011-01-11 18:58 ` Roy Keene [this message]
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=Pine.LNX.4.64.1101111254530.1805@claw.oc9.org \
--to=linux-raid@rkeene.org \
--cc=linux-raid@vger.kernel.org \
--cc=richguk@gmail.com \
--cc=rm@romanrm.ru \
--cc=zkaspar82@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).