linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] will pvmove'ing (an LV at a time) defragment?
Date: Sat, 01 May 2010 18:19:23 -0400	[thread overview]
Message-ID: <1272752363.10234.15.camel@faldara> (raw)
In-Reply-To: <loom.20100501T152029-422@post.gmane.org>

On Sat, 2010-05-01 at 13:26 +0000, Brian J. Murrell wrote:
> That said, it is quite easy to move portions of an LV, so hooking pvmove into
> a disk defragmentation algorithm shouldn't be difficult, if one can find a good 
> defragmentation algorithm.

There isn't really any need; having an lv split in 2 or 3 parts isn't
going to cause any slowdown you can notice outside of a synthetic
sequential access benchmark.

      reply	other threads:[~2010-05-01 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 16:59 [linux-lvm] will pvmove'ing (an LV at a time) defragment? Brian J. Murrell
2010-04-29 18:13 ` Alasdair G Kergon
2010-04-29 18:23 ` Phillip Susi
2010-05-01 13:26 ` Brian J. Murrell
2010-05-01 22:19   ` Phillip Susi [this message]

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=1272752363.10234.15.camel@faldara \
    --to=psusi@cfl.rr.com \
    --cc=linux-lvm@redhat.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).