From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LV Fragmentation determination
Date: Thu Nov 7 11:05:01 2002 [thread overview]
Message-ID: <20021107180002.B8382@sistina.com> (raw)
In-Reply-To: <20021106133803.GA22411@reti>; from joe@fib011235813.fsnet.co.uk on Wed, Nov 06, 2002 at 01:38:03PM +0000
On Wed, Nov 06, 2002 at 01:38:03PM +0000, Joe Thornber wrote:
> On Wed, Nov 06, 2002 at 02:17:00PM +0100, Anders Widman wrote:
> > >> First off, can LV's become fragmented across a PV/VG? If yes then...
> >
> > > Yes, they can.
> >
> > >>
> > >> I'm looking for an easy way to determine how fragmented an LV might been
> > >> inside the VG. Is there any command I can run that'll give me nice
> > >> estimate on this?
> >
> > > You can analyze the "lvdisplay -v" output on your LVs in question.
> > > That shows you the mapping information and therefore, if your LVs are
> > > fragemented.
> >
> > Will LVM include a defragment procedure?
>
> LVM2 will at some point, in that arbitrary remappings will be
> supported. However I'm not convinced that this is a big problem, the
> extents are 4M after all.
True.
BTW: the default got changed to 32MB to support up to 2TB LVs in
LVM 1.0.6 by default rather than by "vgchange -s" which makes the
impact even smaller.
>
> - Joe
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2002-11-07 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-06 2:24 [linux-lvm] LV Fragmentation determination Donald Thompson
2002-11-06 3:20 ` Jon Bendtsen
2002-11-06 7:00 ` Heinz J . Mauelshagen
2002-11-06 7:17 ` Anders Widman
2002-11-06 7:38 ` Joe Thornber
2002-11-07 11:05 ` Heinz J . Mauelshagen [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=20021107180002.B8382@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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.