From: Peter Rajnoha <prajnoha@redhat.com>
To: Jack.Allen@mckesson.com
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LE to PE mapping
Date: Mon, 15 Sep 2014 08:40:50 +0200 [thread overview]
Message-ID: <541689F2.8060709@redhat.com> (raw)
In-Reply-To: <4A8A2A3D96DD154BAD2EE08C0FFFBE5A815067BF@NDHEP50004.na.corp.mckesson.com>
On 09/13/2014 12:02 AM, Allen, Jack wrote:
> Hello:
> I need to find a command on RHEL 5.8 that will show each LE to
> PE mapping for a LV. All the command I have looked at so far (lvs, pvs,
> lvdisplay and pvdisplay) using various option only show the start PE and
> how many.
Try lvdisplay --maps (or pvdisplay --maps for the other way round).
> Something else I need some clarification on is the PE size of
> 4MB and the strip size of 16K. Are the PEs not allocated as shown above
> in either example?
>
> Are the PE allocated in 4MB chunks?
>
Yes, it's 4MB extent size by default if not speficied otherwise
using vgcreate/vgchange -s.
> Then what does the 16K do?
>
That is stripe size - the data will be placed/rotated over disks
by this amount for each disk while the extent size is the basic unit
for mapping LV segments to the underlying disks. Of course, if you have,
for example, 2 stripes, you need an LV which is mapped to at least 2
different disks which also means at least 2 PEs to fulfill this condition
(otherwise, we couldn't map stripes onto different disks which would defeat
the essence of striping) - LVM does this rounding for you and
modifies the LV size automatically to make the stripe count and
LV mapping combination possible.
> -------------------------
> Jackson C. Allen
> McKesson Provider Technologies
> 5995 Windward Parkway
> Alpharetta, GA 30005
> (404) 338-2023
> _Jack.Allen@McKesson.com_ <mailto:Jack.Allen@McKesson.com>
> Confidentiality Notice: This e-mail message, including any attachments,
> is for the sole use of the intended recipient(s) and may contain
> confidential and privileged information. Any unauthorized review, use,
> disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of the original message.
>
>
>
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
--
Peter
next prev parent reply other threads:[~2014-09-15 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 22:02 [linux-lvm] LE to PE mapping Allen, Jack
2014-09-15 6:40 ` Peter Rajnoha [this message]
2014-09-15 14:28 ` Allen, Jack
2014-09-16 17:46 ` Allen, Jack
2014-09-24 4:57 ` Brassow Jonathan
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=541689F2.8060709@redhat.com \
--to=prajnoha@redhat.com \
--cc=Jack.Allen@mckesson.com \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).