From: Anthony Johnson <anthony@storix.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Allocation policies
Date: Tue Sep 10 14:08:26 2002 [thread overview]
Message-ID: <3D7E4135.9EE88518@storix.com> (raw)
I know there are 2 allocation policies, contiguous and next free. Is
there any information that describes in detail how LVM determines the
extents to assign to a logical volume with it is created or extended?
For example, if the policy is "contiguous", must the LV contain all
contiguous extents or does it use a "best-case" scenario, and how would
that work? Likewise, in the "next free" scenario, is there any weight
given to contiguous space, does it automatically allocate across PVs,
etc?
Thanks!
Anthony
next reply other threads:[~2002-09-10 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 14:08 Anthony Johnson [this message]
2002-09-11 5:53 ` [linux-lvm] Allocation policies 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=3D7E4135.9EE88518@storix.com \
--to=anthony@storix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox