From: Dieter Stueken <stueken@conterra.de>
To: linux-lvm@sistina.com
Subject: [linux-lvm] 64K limit for VG/LV
Date: Tue Jan 22 06:59:01 2002 [thread overview]
Message-ID: <3C4D61CF.12330DF1@conterra.de> (raw)
I just merged two volume groups without any error message,
but the result seems to have more than 65535 LE now. The only
effect until now is, that the number of free PE becomes negative
and is displayed as an unsigned huge value:
--- Volume group ---
VG Name vg0
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 9
Open LV 2
MAX LV Size 255.99 GB
Max PV 256
Cur PV 4
Act PV 4
VG Size 286.33 GB
PE Size 4.00 MB
Total PE 73300
Alloc PE / Size 97200 / 379.69 GB
Free PE / Size 4294943396 / 1.91 TB
VG UUID QDKBpV-xwqr-gO3b-VKiA-Jaf4-grmm-pWEY32
My VG consists of 4 x 75 GB IBM-DTLA-307075. Should I worry now?
If there is any limit of 65536 I might suspect some 16bit value
for PE addressing. If no overflow is checked, a wrong PE may be
addressed beyond LE 65536 and my VG possibly gets destroyed :-(
But I found some hints in the mailing archive, saying that the
64K limit does not affect the VG itself but only each LV inside.
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.
Besides, vgdisplay says: "Logical Volume Manager 1.0.1-rc2"
On SuSE 7.3 running 2.4.16.
If I want to increase my LE size, I think I have to create a new VG.
Is there any tool to copy my LVs to the new VG other than "dd"?
Dieter.
--
Dieter St�ken, con terra GmbH, M�nster
stueken@conterra.de stueken@qgp.uni-muenster.de
http://www.conterra.de/ http://qgp.uni-muenster.de/~stueken
(0)251-980-2027 (0)251-83-334974
next reply other threads:[~2002-01-22 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 6:59 Dieter Stueken [this message]
2002-01-22 12:44 ` [linux-lvm] 64K limit for VG/LV Heinz J . Mauelshagen
2002-01-23 12:59 ` Dieter Stueken
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=3C4D61CF.12330DF1@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 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.