From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] HUGE LVM log file...
Date: Wed, 18 Jul 2001 09:22:01 +0100 [thread overview]
Message-ID: <20010718092201.C382@btconnect.com> (raw)
In-Reply-To: <85063BBE668FD411944400D0B744267A643448@AUSMAIL>; from austin@coremetrics.com on Tue, Jul 17, 2001 at 04:52:21PM -0500
On Tue, Jul 17, 2001 at 04:52:21PM -0500, Gonyou, Austin wrote:
> Is there a how-to or cookbook type doc which tells how/why you should setup
> your LE/PE's? Outter tracks/inner tracks, speed areas, etc?
> Theory around this is a good thing with relation to LVM and using it. Any
> ideas on that?
We've not had much feedback on this, I guess that people don't really
notice much of a difference, I certainly haven't. The allocation
policy for PE's is to start at the beginning of the disk (which tend
to have faster data transfer rates) and work back. Anybody done any
benchmarking in this area ?
- Joe
next prev parent reply other threads:[~2001-07-18 8:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 21:52 [linux-lvm] HUGE LVM log file Gonyou, Austin
2001-07-18 0:00 ` Wolfgang Weisselberg
2001-07-18 8:22 ` Joe Thornber [this message]
2001-07-18 8:48 ` Benoit SERRA
2001-07-18 9:33 ` Joe Thornber
2001-07-18 19:23 ` Ragnar Kjørstad
2001-07-18 22:22 ` lembark
2001-07-18 9:46 ` Adam Cioccarelli
[not found] ` <Pine.LNX.4.33.0107181141480.25686-100000@vie-ac.office.ece tra.com>
2001-07-18 9:47 ` Benoit SERRA
2001-07-18 10:48 ` [linux-lvm] what happens when hdX get hdY in a VG Oliver Jovic
2001-07-18 10:59 ` Joe Thornber
2001-07-18 13:29 ` [linux-lvm] HUGE LVM log file Iain Campbell
2001-07-18 17:02 ` Steven Lembark
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 11:13 Guennadi Liakhovetski
2001-07-17 11:14 ` Heinz J. Mauelshagen
2001-07-17 11:28 ` Guennadi Liakhovetski
2001-07-17 11:28 ` Heinz J. Mauelshagen
2001-07-17 21:28 ` Wolfgang Weisselberg
2001-07-18 14:55 ` 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=20010718092201.C382@btconnect.com \
--to=thornber@btconnect.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.