From: Dieter Stueken <stueken@conterra.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] 64K limit for VG/LV
Date: Wed Jan 23 12:59:02 2002 [thread overview]
Message-ID: <3C4F07E6.E137C465@conterra.de> (raw)
In-Reply-To: 20020122193953.A25782@sistina.com
"Heinz J . Mauelshagen" schrieb:
> that's correct. It is just a per LV limit for the max amount of its
> Logical Extents (LEs).
>
> > Thus as long as each of my LV is <256G I don't have to worry, and
> > the reported "Free PE" might be just cosmetics.
>
> Cosmetics is a nice way to put it :-)
> We probably have missed that one, because for a VG with such a large capacity
> we choosed larger PE sizes.
but I still worry a bit about my data. The reason for the wrong "Free
PE"
reported seems not to be the 64k limit, but the fact that some of my LVs
are reported/counted twice!
-> vgdisplay -v vg0 | fgrep "LV Name"
LV Name /dev/vg0/root
LV Name /dev/vg0/win2k
LV Name /dev/vg0/ortho
LV Name /dev/vg0/praktikum
LV Name /dev/vg0/swap
LV Name /dev/vg0/mirror
LV Name /dev/vg0/disk_huetti
LV Name /dev/vg0/SuSE-7.3
LV Name /dev/vg0/mirror <<<<<
LV Name /dev/vg0/disk_huetti <<<<<
Thus I still fear of some evil inconsistencies for my data.
Is there any tool available like "e2fsck" for LVM to resolve such a
problem?
Dieter.
prev parent reply other threads:[~2002-01-23 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 6:59 [linux-lvm] 64K limit for VG/LV Dieter Stueken
2002-01-22 12:44 ` Heinz J . Mauelshagen
2002-01-23 12:59 ` Dieter Stueken [this message]
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=3C4F07E6.E137C465@conterra.de \
--to=stueken@conterra.de \
--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