From: Roman Mamedov <rm@romanrm.ru>
To: David Brown <david.brown@hesbynett.no>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm does not create partition devices whatsoever, "partitionable" functionality broken
Date: Sat, 14 May 2011 16:24:27 +0600 [thread overview]
Message-ID: <20110514162427.143668d6@natsu> (raw)
In-Reply-To: <iqlkfg$1s9$1@dough.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Sat, 14 May 2011 12:10:56 +0200
David Brown <david.brown@hesbynett.no> wrote:
> What is perhaps more relevant, is can filesystems see the fragmentation
> of the LV's? I don't know the answer.
No, of course they can't.
> Still, you don't usually have many segments in an LV - if you want the
> LV to be fast, you can request it to be contiguous when creating it.
> Then you only get a fragment for each time it is grown. It's a price
> often worth paying for the flexibility.
From what I see, the key selling point for LVM is the ability to 'easily'
add/remove/resize LVs. And then if you buy that and start to actively use
these features, you end up in a situation (badly fragmented LVs) from which
there isn't a proper way out. No - backup and restore, or 'have enough
contiguous free space to mirror your entire LV and then nuke the original' are
not the answer. What's sad is that there isn't any fundamental technical
reason LVs can't be defragmented. They can, just no one has bothered to write
the corresponding code yet.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-14 10:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 15:13 mdadm does not create partition devices whatsoever, "partitionable" functionality broken Christopher White
2011-05-13 16:49 ` Phil Turmel
2011-05-13 17:18 ` Christopher White
2011-05-13 17:32 ` Christopher White
2011-05-13 17:40 ` Roman Mamedov
2011-05-13 18:04 ` Christopher White
2011-05-13 18:18 ` Phil Turmel
2011-05-13 18:54 ` Christopher White
2011-05-13 19:01 ` Rudy Zijlstra
2011-05-13 19:49 ` Christopher White
2011-05-13 20:00 ` Rudy Zijlstra
2011-05-13 19:49 ` Christopher White
2011-05-13 19:22 ` Phil Turmel
2011-05-13 19:32 ` Roman Mamedov
2011-05-13 19:39 ` Phil Turmel
2011-05-14 10:10 ` David Brown
2011-05-14 10:24 ` Roman Mamedov [this message]
2011-05-14 12:56 ` David Brown
2011-05-14 13:27 ` Drew
2011-05-14 18:21 ` David Brown
2011-05-13 17:43 ` Phil Turmel
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=20110514162427.143668d6@natsu \
--to=rm@romanrm.ru \
--cc=david.brown@hesbynett.no \
--cc=linux-raid@vger.kernel.org \
/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).