From: Jon Bendtsen <jon+lvm@silicide.dk>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LV Fragmentation determination
Date: Wed Nov 6 03:20:01 2002 [thread overview]
Message-ID: <3DC8DE98.FBFF5B8@silicide.dk> (raw)
In-Reply-To: Pine.LNX.4.44.0211060108110.8692-100000@junior.lunanet.biz
Donald Thompson wrote:
>
> First off, can LV's become fragmented across a PV/VG? If yes then...
yes they can. But that depends on how you made it. The default is to
use the next free PE, but you can specify the PE's.
> 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?
i dont know, but cant you use lvdisplay, pvdisplay, or the other
display commands to see the PE numbers ?
> Assuming theres no such command, can I determine this by looking at the
> PE's displayed from an 'lvdisplay -v' command? I'm guessing it'd be pretty
> easy to write a script that analyzes the PE numbers and looks for skips in
> the sequence to give myself an idea of the amount of fragmention for the
> LV. Or am I competely wrong thinking you can use PE's to make such a
> determination?
i think you can
> I do shrinks and enlarges for different LV's sometimes on an almost daily
> basis, and my VG's are getting to be very old. So I'm curious to see how
> fragmentated my LVs have become.
Properly much, but is that bad ? I mean, sure you have to move the head
every PE size, but how big are your PE size ? The default is 4MB.
JonB
next prev parent reply other threads:[~2002-11-06 3:20 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 [this message]
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
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=3DC8DE98.FBFF5B8@silicide.dk \
--to=jon+lvm@silicide.dk \
--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.