* Re: [linux-lvm] vgextend segfaults
2001-01-24 14:35 [linux-lvm] vgextend segfaults wim bakker
@ 2001-01-24 13:57 ` lewis
2001-01-24 14:18 ` Joe Thornber
2001-01-24 19:28 ` Heinz J. Mauelshagen
2 siblings, 0 replies; 4+ messages in thread
From: lewis @ 2001-01-24 13:57 UTC (permalink / raw)
To: linux-lvm
[-- Attachment #1: Type: text/plain, Size: 9008 bytes --]
On Wed, Jan 24, 2001 at 03:35:30PM +0100, wim bakker wrote:
> Hai,
> setup: RH7 with all updates applied
> kernel: 2.4.0 and 2.4.1-pre10
> LVM: tried 0.9, 0.9.1-beta1 and 0.9.1-beta2
> with fdisk I created 4 primary partitions on a testdrive all
> 8e.
Ok, this may be a silly question, but did you apply the LVM 0.9.1_beta2
kernel patch to 2.4.0 and recompile the kernel? If you did not, it would
not be surprising that you are getting this error. Look at the README in
the PATCHES directory for information on generating a 0.9.1 Beta2 patch.
> After that I do a pvcreate for those 4 partitiions:
> --------------------------------
> [root@water 0.9]# pvcreate -v /dev/sdb1
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/sdb1"
> pvcreate -- getting physical volume size
> pvcreate -- checking partition type
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/sdb1 with
> 3212937 sectors
> pvcreate -- writing physical volume data to disk "/dev/sdb1"
> pvcreate -- physical volume "/dev/sdb1" successfully created
> pvcreate -- unlocking logical volume manager
>
> [root@water 0.9]# pvcreate -v /dev/sdb2
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/sdb2"
> pvcreate -- getting physical volume size
> pvcreate -- checking partition type
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/sdb2 with
> 3213000 sectors
> pvcreate -- writing physical volume data to disk "/dev/sdb2"
> pvcreate -- physical volume "/dev/sdb2" successfully created
> pvcreate -- unlocking logical volume manager
>
> [root@water 0.9]# pvcreate -v /dev/sdb3
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/sdb3"
> pvcreate -- getting physical volume size
> pvcreate -- checking partition type
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/sdb3 with
> 6426000 sectors
> pvcreate -- writing physical volume data to disk "/dev/sdb3"
> pvcreate -- physical volume "/dev/sdb3" successfully created
> pvcreate -- unlocking logical volume manager
>
> [root@water 0.9]# pvcreate -v /dev/sdb4
> pvcreate -- locking logical volume manager
> pvcreate -- checking physical volume name "/dev/sdb4"
> pvcreate -- getting physical volume size
> pvcreate -- checking partition type
> pvcreate -- creating new physical volume
> pvcreate -- setting up physical volume for /dev/sdb4 with
> 5076540 sectors
> pvcreate -- writing physical volume data to disk "/dev/sdb4"
> pvcreate -- physical volume "/dev/sdb4" successfully created
> pvcreate -- unlocking logical volume manager
> -----------------------------------
> then I do a vgscan
> -----------------------------
> [root@water 0.9]# vgscan
> vgscan -- reading all physical volumes (this may take a
> while...)
> vgscan -- no volume groups found
> --------------------------------------
> then I do a vgcreate:
> --------------------------------------
> [root@water 0.9]# vgcreate -A y -l 10 -p 20 -s 4M -v testl
> /dev/sdb1
> vgcreate -- checking volume group name
> vgcreate -- checking volume group directory existence
> vgcreate -- locking logical volume manager
> vgcreate -- checking volume group "testl" existence
> vgcreate -- counting all existing volume groups
> vgcreate -- reading all physical volume data from disks
> vgcreate -- checking if all given physical volumes in
> command line are new
> vgcreate -- checking physical volumes name "/dev/sdb1"
> vgcreate -- checking physical volume "/dev/sdb1"
> vgcreate -- getting size of physical volume "/dev/sdb1"
> vgcreate -- size of physical volume "/dev/sdb1" is 3212937
> sectors
> vgcreate -- checking for new physical volume "/dev/sdb1"
> vgcreate -- checking for identical physical volumes on
> command line
> vgcreate -- 1 physical volume will be inserted into volume
> group "testl"
> vgcreate -- checking command line arguments
> vgcreate -- INFO: maximum of 20 physical volumes
> vgcreate -- INFO: maximum of 10 logical volumes
> vgcreate -- setting up volume data for creation
> vgcreate -- INFO: maximum logical volume size is 255.99
> Gigabyte
> vgcreate -- storing volume group data on disk(s)
> vgcreate -- removing any invalid special files of volume
> group "testl"
> vgcreate -- creating volume group directory /dev/testl
> vgcreate -- creating VGDA for volume group "testl" in kernel
> vgcreate -- inserting volume group "testl" into
> "/etc/lvmtab"
> vgcreate -- checking volume group name "testl"
> vgcreate -- checking volume group consistency of "testl"
> vgcreate -- checking existence of "/etc/lvmtab.d"
> vgcreate -- storing volume group data of "testl" in
> "/etc/lvmtab.d/testl.tmp"
> vgcreate -- storing physical volume data of "testl" in
> "/etc/lvmtab.d/testl.tmp"
> vgcreate -- storing logical volume data of volume group
> "testl" in "/etc/lvmtab.d/testl.tmp"
> vgcreate -- renaming "/etc/lvmtab.d/testl.tmp" to
> "/etc/lvmtab.d/testl"
> vgcreate -- doing automatic backup of volume group "testl"
> vgcreate -- checking volume group name "testl"
> vgcreate -- checking volume group consistency of "testl"
> vgcreate -- checking existence of "/etc/lvmconf"
> vgcreate -- making directory "/etc/lvmconf"
> vgcreate -- storing volume group data of "testl" in
> "/etc/lvmconf/testl.conf.tmp"
> vgcreate -- storing physical volume data of "testl" in
> "/etc/lvmconf/testl.conf.tmp"
> vgcreate -- storing logical volume data of volume group
> "testl" in "/etc/lvmconf/testl.conf.tmp"
> vgcreate -- checking existence of
> "/etc/lvmconf/testl.conf.tmp"
> vgcreate -- checking existence of "/etc/lvmconf/testl.conf"
> vgcreate -- renaming "/etc/lvmconf/testl.conf.tmp" to
> "/etc/lvmconf/testl.conf"
> vgcreate -- unlocking logical volume manager
> vgcreate -- volume group "testl" successfully created and
> activated
>
> [root@water 0.9]# vgdisplay -v
> --- Volume group ---
> VG Name testl
> VG Access read/write
> VG Status available/resizable
> VG # 0
> MAX LV 10
> Cur LV 0
> Open LV 0
> MAX LV Size 255.99 GB
> Max PV 20
> Cur PV 1
> Act PV 1
> VG Size 1.53 GB
> PE Size 4 MB
> Total PE 392
> Alloc PE / Size 0 / 0
> Free PE / Size 392 / 1.53 GB
> VG UUID ZUVQqV-cWzF-W0Ce-qJPk-wTN5-qKX3-PyNPeC
>
> --- No logical volumes defined in testl ---
>
>
> --- Physical volumes ---
> PV Name (#) /dev/sdb1 (1)
> PV Status available / allocatable
> Total PE / Free PE 392 / 392
> --------------------------------------
> Then I do a vgextend:
> --------------------------------------
> vgextend -v testl /dev/sdb2
> vgextend -- locking logical volume manager
> vgextend -- checking volume group name "testl"
> vgextend -- checking volume group "testl" existence
> vgextend -- checking for inactivity of volume group
> vgextend -- reading data of volume group "testl" from lvmtab
> vgextend -- INFO: maximum logical volume size is 255.99
> Gigabyte
> vgextend -- reading data for all physical volumes from
> disk(s)
> vgextend -- extending VGDA structures of volume group
> "testl"
> vgextend -- volume group "testl" will be extended by 1 new
> physical volumes
> vgextend -- extending volume group "testl" by physical
> volume "/dev/sdb2" in kernel
> Segmentation fault
> ----------------------------------------
> It segfaults , it segfaults whatever 2.4.0 or 2.4.1-prexxx
> I use, I tried this with the above mentioned lvm's
> and allways the same result. a segfault .
> Now what am I doink wrong???
> I tried this on two different machine one dual processor
> with
> adaptec 29160 adapter and one with 53c875 adapter
> both with the same disks quantum 9Gb u2w disks
> TIA
>
> wim bakker
> ComNed Netwerken BV
> 31 20 4350025
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
AJ Lewis
Sistina Software Inc. Voice: 612-379-3951
1313 5th St SE, Suite 111 Fax: 612-379-3952
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
There's nary an animal alive that can outrun a greased Scotsman.
- Groundskeeper Willie
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [linux-lvm] vgextend segfaults
2001-01-24 14:35 [linux-lvm] vgextend segfaults wim bakker
2001-01-24 13:57 ` lewis
@ 2001-01-24 14:18 ` Joe Thornber
2001-01-24 19:28 ` Heinz J. Mauelshagen
2 siblings, 0 replies; 4+ messages in thread
From: Joe Thornber @ 2001-01-24 14:18 UTC (permalink / raw)
To: linux-lvm
On Wed, Jan 24, 2001 at 03:35:30PM +0100, wim bakker wrote:
> Hai,
> setup: RH7 with all updates applied
> kernel: 2.4.0 and 2.4.1-pre10
> LVM: tried 0.9, 0.9.1-beta1 and 0.9.1-beta2
> with fdisk I created 4 primary partitions on a testdrive all
> 8e.
Use beta2.
Are you patching and rebuilding the LVM kernel driver as well as building
the tools ?
- Joe
^ permalink raw reply [flat|nested] 4+ messages in thread
* [linux-lvm] vgextend segfaults
@ 2001-01-24 14:35 wim bakker
2001-01-24 13:57 ` lewis
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: wim bakker @ 2001-01-24 14:35 UTC (permalink / raw)
To: linux-lvm
Hai,
setup: RH7 with all updates applied
kernel: 2.4.0 and 2.4.1-pre10
LVM: tried 0.9, 0.9.1-beta1 and 0.9.1-beta2
with fdisk I created 4 primary partitions on a testdrive all
8e.
After that I do a pvcreate for those 4 partitiions:
--------------------------------
[root@water 0.9]# pvcreate -v /dev/sdb1
pvcreate -- locking logical volume manager
pvcreate -- checking physical volume name "/dev/sdb1"
pvcreate -- getting physical volume size
pvcreate -- checking partition type
pvcreate -- creating new physical volume
pvcreate -- setting up physical volume for /dev/sdb1 with
3212937 sectors
pvcreate -- writing physical volume data to disk "/dev/sdb1"
pvcreate -- physical volume "/dev/sdb1" successfully created
pvcreate -- unlocking logical volume manager
[root@water 0.9]# pvcreate -v /dev/sdb2
pvcreate -- locking logical volume manager
pvcreate -- checking physical volume name "/dev/sdb2"
pvcreate -- getting physical volume size
pvcreate -- checking partition type
pvcreate -- creating new physical volume
pvcreate -- setting up physical volume for /dev/sdb2 with
3213000 sectors
pvcreate -- writing physical volume data to disk "/dev/sdb2"
pvcreate -- physical volume "/dev/sdb2" successfully created
pvcreate -- unlocking logical volume manager
[root@water 0.9]# pvcreate -v /dev/sdb3
pvcreate -- locking logical volume manager
pvcreate -- checking physical volume name "/dev/sdb3"
pvcreate -- getting physical volume size
pvcreate -- checking partition type
pvcreate -- creating new physical volume
pvcreate -- setting up physical volume for /dev/sdb3 with
6426000 sectors
pvcreate -- writing physical volume data to disk "/dev/sdb3"
pvcreate -- physical volume "/dev/sdb3" successfully created
pvcreate -- unlocking logical volume manager
[root@water 0.9]# pvcreate -v /dev/sdb4
pvcreate -- locking logical volume manager
pvcreate -- checking physical volume name "/dev/sdb4"
pvcreate -- getting physical volume size
pvcreate -- checking partition type
pvcreate -- creating new physical volume
pvcreate -- setting up physical volume for /dev/sdb4 with
5076540 sectors
pvcreate -- writing physical volume data to disk "/dev/sdb4"
pvcreate -- physical volume "/dev/sdb4" successfully created
pvcreate -- unlocking logical volume manager
-----------------------------------
then I do a vgscan
-----------------------------
[root@water 0.9]# vgscan
vgscan -- reading all physical volumes (this may take a
while...)
vgscan -- no volume groups found
--------------------------------------
then I do a vgcreate:
--------------------------------------
[root@water 0.9]# vgcreate -A y -l 10 -p 20 -s 4M -v testl
/dev/sdb1
vgcreate -- checking volume group name
vgcreate -- checking volume group directory existence
vgcreate -- locking logical volume manager
vgcreate -- checking volume group "testl" existence
vgcreate -- counting all existing volume groups
vgcreate -- reading all physical volume data from disks
vgcreate -- checking if all given physical volumes in
command line are new
vgcreate -- checking physical volumes name "/dev/sdb1"
vgcreate -- checking physical volume "/dev/sdb1"
vgcreate -- getting size of physical volume "/dev/sdb1"
vgcreate -- size of physical volume "/dev/sdb1" is 3212937
sectors
vgcreate -- checking for new physical volume "/dev/sdb1"
vgcreate -- checking for identical physical volumes on
command line
vgcreate -- 1 physical volume will be inserted into volume
group "testl"
vgcreate -- checking command line arguments
vgcreate -- INFO: maximum of 20 physical volumes
vgcreate -- INFO: maximum of 10 logical volumes
vgcreate -- setting up volume data for creation
vgcreate -- INFO: maximum logical volume size is 255.99
Gigabyte
vgcreate -- storing volume group data on disk(s)
vgcreate -- removing any invalid special files of volume
group "testl"
vgcreate -- creating volume group directory /dev/testl
vgcreate -- creating VGDA for volume group "testl" in kernel
vgcreate -- inserting volume group "testl" into
"/etc/lvmtab"
vgcreate -- checking volume group name "testl"
vgcreate -- checking volume group consistency of "testl"
vgcreate -- checking existence of "/etc/lvmtab.d"
vgcreate -- storing volume group data of "testl" in
"/etc/lvmtab.d/testl.tmp"
vgcreate -- storing physical volume data of "testl" in
"/etc/lvmtab.d/testl.tmp"
vgcreate -- storing logical volume data of volume group
"testl" in "/etc/lvmtab.d/testl.tmp"
vgcreate -- renaming "/etc/lvmtab.d/testl.tmp" to
"/etc/lvmtab.d/testl"
vgcreate -- doing automatic backup of volume group "testl"
vgcreate -- checking volume group name "testl"
vgcreate -- checking volume group consistency of "testl"
vgcreate -- checking existence of "/etc/lvmconf"
vgcreate -- making directory "/etc/lvmconf"
vgcreate -- storing volume group data of "testl" in
"/etc/lvmconf/testl.conf.tmp"
vgcreate -- storing physical volume data of "testl" in
"/etc/lvmconf/testl.conf.tmp"
vgcreate -- storing logical volume data of volume group
"testl" in "/etc/lvmconf/testl.conf.tmp"
vgcreate -- checking existence of
"/etc/lvmconf/testl.conf.tmp"
vgcreate -- checking existence of "/etc/lvmconf/testl.conf"
vgcreate -- renaming "/etc/lvmconf/testl.conf.tmp" to
"/etc/lvmconf/testl.conf"
vgcreate -- unlocking logical volume manager
vgcreate -- volume group "testl" successfully created and
activated
[root@water 0.9]# vgdisplay -v
--- Volume group ---
VG Name testl
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 10
Cur LV 0
Open LV 0
MAX LV Size 255.99 GB
Max PV 20
Cur PV 1
Act PV 1
VG Size 1.53 GB
PE Size 4 MB
Total PE 392
Alloc PE / Size 0 / 0
Free PE / Size 392 / 1.53 GB
VG UUID ZUVQqV-cWzF-W0Ce-qJPk-wTN5-qKX3-PyNPeC
--- No logical volumes defined in testl ---
--- Physical volumes ---
PV Name (#) /dev/sdb1 (1)
PV Status available / allocatable
Total PE / Free PE 392 / 392
--------------------------------------
Then I do a vgextend:
--------------------------------------
vgextend -v testl /dev/sdb2
vgextend -- locking logical volume manager
vgextend -- checking volume group name "testl"
vgextend -- checking volume group "testl" existence
vgextend -- checking for inactivity of volume group
vgextend -- reading data of volume group "testl" from lvmtab
vgextend -- INFO: maximum logical volume size is 255.99
Gigabyte
vgextend -- reading data for all physical volumes from
disk(s)
vgextend -- extending VGDA structures of volume group
"testl"
vgextend -- volume group "testl" will be extended by 1 new
physical volumes
vgextend -- extending volume group "testl" by physical
volume "/dev/sdb2" in kernel
Segmentation fault
----------------------------------------
It segfaults , it segfaults whatever 2.4.0 or 2.4.1-prexxx
I use, I tried this with the above mentioned lvm's
and allways the same result. a segfault .
Now what am I doink wrong???
I tried this on two different machine one dual processor
with
adaptec 29160 adapter and one with 53c875 adapter
both with the same disks quantum 9Gb u2w disks
TIA
wim bakker
ComNed Netwerken BV
31 20 4350025
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [linux-lvm] vgextend segfaults
2001-01-24 14:35 [linux-lvm] vgextend segfaults wim bakker
2001-01-24 13:57 ` lewis
2001-01-24 14:18 ` Joe Thornber
@ 2001-01-24 19:28 ` Heinz J. Mauelshagen
2 siblings, 0 replies; 4+ messages in thread
From: Heinz J. Mauelshagen @ 2001-01-24 19:28 UTC (permalink / raw)
To: linux-lvm
Looks like you didn't patch the kernel with the patch contained
in the LVM distribution.
Did you follow PATCHES/README in order to do that?
On Wed, Jan 24, 2001 at 03:35:30PM +0100, wim bakker wrote:
> Hai,
> setup: RH7 with all updates applied
> kernel: 2.4.0 and 2.4.1-pre10
> LVM: tried 0.9, 0.9.1-beta1 and 0.9.1-beta2
> with fdisk I created 4 primary partitions on a testdrive all
> 8e.
> After that I do a pvcreate for those 4 partitiions:
<SNIP>
> Then I do a vgextend:
> --------------------------------------
> vgextend -v testl /dev/sdb2
> vgextend -- locking logical volume manager
> vgextend -- checking volume group name "testl"
> vgextend -- checking volume group "testl" existence
> vgextend -- checking for inactivity of volume group
> vgextend -- reading data of volume group "testl" from lvmtab
> vgextend -- INFO: maximum logical volume size is 255.99
> Gigabyte
> vgextend -- reading data for all physical volumes from
> disk(s)
> vgextend -- extending VGDA structures of volume group
> "testl"
> vgextend -- volume group "testl" will be extended by 1 new
> physical volumes
> vgextend -- extending volume group "testl" by physical
> volume "/dev/sdb2" in kernel
> Segmentation fault
> ----------------------------------------
> It segfaults , it segfaults whatever 2.4.0 or 2.4.1-prexxx
> I use, I tried this with the above mentioned lvm's
> and allways the same result. a segfault .
> Now what am I doink wrong???
> I tried this on two different machine one dual processor
> with
> adaptec 29160 adapter and one with 53c875 adapter
> both with the same disks quantum 9Gb u2w disks
> TIA
>
> wim bakker
> ComNed Netwerken BV
> 31 20 4350025
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-01-24 19:28 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-01-24 14:35 [linux-lvm] vgextend segfaults wim bakker
2001-01-24 13:57 ` lewis
2001-01-24 14:18 ` Joe Thornber
2001-01-24 19:28 ` Heinz J. Mauelshagen
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).