All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] LV Fragmentation determination
@ 2002-11-06  2:24 Donald Thompson
  2002-11-06  3:20 ` Jon Bendtsen
  2002-11-06  7:00 ` Heinz J . Mauelshagen
  0 siblings, 2 replies; 6+ messages in thread
From: Donald Thompson @ 2002-11-06  2:24 UTC (permalink / raw)
  To: linux-lvm

First off, can LV's become fragmented across a PV/VG? If yes then...

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?

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 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.

TIA for any clues.

-Don

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [linux-lvm] LV Fragmentation determination
  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
  1 sibling, 0 replies; 6+ messages in thread
From: Jon Bendtsen @ 2002-11-06  3:20 UTC (permalink / raw)
  To: linux-lvm

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [linux-lvm] LV Fragmentation determination
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Heinz J . Mauelshagen @ 2002-11-06  7:00 UTC (permalink / raw)
  To: linux-lvm

On Wed, Nov 06, 2002 at 01:23:52AM -0700, Donald Thompson 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?
> 
> 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 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.

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.

> 
> TIA for any clues.
> 
> -Don
> 
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [linux-lvm] LV Fragmentation determination
  2002-11-06  7:00 ` Heinz J . Mauelshagen
@ 2002-11-06  7:17   ` Anders Widman
  2002-11-06  7:38     ` Joe Thornber
  0 siblings, 1 reply; 6+ messages in thread
From: Anders Widman @ 2002-11-06  7:17 UTC (permalink / raw)
  To: Heinz J . Mauelshagen

>> 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?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [linux-lvm] LV Fragmentation determination
  2002-11-06  7:17   ` Anders Widman
@ 2002-11-06  7:38     ` Joe Thornber
  2002-11-07 11:05       ` Heinz J . Mauelshagen
  0 siblings, 1 reply; 6+ messages in thread
From: Joe Thornber @ 2002-11-06  7:38 UTC (permalink / raw)
  To: linux-lvm

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.

- Joe

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [linux-lvm] LV Fragmentation determination
  2002-11-06  7:38     ` Joe Thornber
@ 2002-11-07 11:05       ` Heinz J . Mauelshagen
  0 siblings, 0 replies; 6+ messages in thread
From: Heinz J . Mauelshagen @ 2002-11-07 11:05 UTC (permalink / raw)
  To: linux-lvm

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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2002-11-07 11:05 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.