All of lore.kernel.org
 help / color / mirror / Atom feed
* [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4
@ 2001-10-29 19:57 Jean-Noel GADREAU
  2001-10-30  3:09 ` Nils Juergens
  2001-10-30  9:46 ` Gaziz Nugmanov
  0 siblings, 2 replies; 4+ messages in thread
From: Jean-Noel GADREAU @ 2001-10-29 19:57 UTC (permalink / raw)
  To: linux-lvm

Hi.

I have a problem to extend my current volume group "vg01". I did:

# pvcreate /dev/hde1 /dev/hde2
pvcreate -- physical volume "/dev/hde1" successfully created
pvcreate -- physical volume "/dev/hde2" successfully created

# vgextend -v vg01 /dev/hde1
vgextend -- locking logical volume manager
vgextend -- checking volume group name "vg01"
vgextend -- checking volume group "vg01" existence
vgextend -- checking for inactivity of volume group
vgextend -- reading data of volume group "vg01" 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 "vg01"
vgextend -- volume group "vg01" will be extended by 1 new physical volumes
vgextend -- extending volume group "vg01" by physical volume "/dev/hde1" 
in kernel
Segmentation fault (core dumped)

I am using RedHat 7.1 with a custom kernel to have LVM (2.4.9-6). I have 
2 drives on this IDE controller (a Promise UltraDMA100DX2) and both work 
fine with linux. My secondary drive (/dev/hdf is already part of vg01).

I don't know if this is a bug or if I am not using this correctly. I 
could not find anything on the internet about this particular problem.

For more information, I am including the results of several commands. 
Let me know if you need more information.

Thanks in advance for your help.
Regards,
Jean-Noel GADREAU

============================================

# vgdisplay -v vg01
--- Volume group ---
VG Name               vg01
VG Access             read/write
VG Status             available/resizable
VG #                  0
MAX LV                256
Cur LV                1
Open LV               1
MAX LV Size           255.99 GB
Max PV                256
Cur PV                1
Act PV                1
VG Size               37.27 GB
PE Size               4.00 MB
Total PE              9541
Alloc PE / Size       9500 / 37.11 GB
Free  PE / Size       41 / 164.00 MB
VG UUID               SCcP8o-73vj-4rCl-GbTx-A0up-5GAu-BEEgVL

--- Logical volume ---
LV Name                /dev/vg01/data
VG Name                vg01
LV Write Access        read/write
LV Status              available
LV #                   1
# open                 1
LV Size                37.11 GB
Current LE             9500
Allocated LE           9500
Allocation             next free
Read ahead sectors     120
Block device           58:0


--- Physical volumes ---
PV Name (#)           /dev/hdf1 (1)
PV Status             available / allocatable
Total PE / Free PE    9541 / 41

=============================================
# vgscan -v
vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- scanning for all active volume group(s) first
vgscan -- found active volume group "vg01"
vgscan -- reading data of volume group "vg01" from physical volume(s)
vgscan -- inserting "vg01" into lvmtab
vgscan -- backing up volume group "vg01"
vgscan -- checking volume group name "vg01"
vgscan -- checking volume group consistency of "vg01"
vgscan -- checking existence of "/etc/lvmtab.d"
vgscan -- storing volume group data of "vg01" in "/etc/lvmtab.d/vg01.tmp"
vgscan -- storing physical volume data of "vg01" in "/etc/lvmtab.d/vg01.tmp"
vgscan -- storing logical volume data of volume group "vg01" in 
"/etc/lvmtab.d/v
g01.tmp"
vgscan -- renaming "/etc/lvmtab.d/vg01.tmp" to "/etc/lvmtab.d/vg01"
vgscan -- removing special files and directory for volume group "vg01"
vgscan -- creating directory and group character special file for "vg01"
vgscan -- creating block device special files for vg01
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume 
group

=============================================
# pvscan -v
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- walking through all physical volumes found
pvscan -- inactive PV "/dev/hde1" is in no VG  [18.64 GB]
pvscan -- inactive PV "/dev/hde2" is in no VG  [18.64 GB]
pvscan -- ACTIVE   PV "/dev/hdf1" of VG "vg01" [37.27 GB / 164.00 MB free]
pvscan -- total: 3 [74.56 GB] / in use: 1 [37.27 GB] / in no VG: 2 
[37.29 GB]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4
  2001-10-29 19:57 [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4 Jean-Noel GADREAU
@ 2001-10-30  3:09 ` Nils Juergens
  2001-10-30 15:13   ` Jean-Noel GADREAU
  2001-10-30  9:46 ` Gaziz Nugmanov
  1 sibling, 1 reply; 4+ messages in thread
From: Nils Juergens @ 2001-10-30  3:09 UTC (permalink / raw)
  To: linux-lvm

On Mon, 29.10.01, Jean-Noel GADREAU <cathjn@gadreau.net> wrote:

[snip]
> vgextend -- extending volume group "vg01" by physical volume "/dev/hde1" 
> in kernel
> Segmentation fault (core dumped)
> 
> I am using RedHat 7.1 with a custom kernel to have LVM (2.4.9-6). I have 
> 2 drives on this IDE controller (a Promise UltraDMA100DX2) and both work 
> fine with linux. My secondary drive (/dev/hdf is already part of vg01).
[snip]

The stock linux kernel comes with an old version of lvm. Please grab
the latest version and make sure to patch your kernel (see
PATCHES/README in the lvm distribution). You should also upgrade your
userspace tools (lvcreate, vgextend and the like).

On a further note, check which compiler you are using. gcc-2.96 should
be used without optimization (-O0) and make sure you do not use
gcc-3.0.x (it produces broken code on some occasions, this happened to
me with the lvm tools).

good luck,

Nils

-- 
 >   Nils Juergens  | nils@muon.de | icq 7090774   <
 >  If we all work hard, we can turn this company  <
 >      around 360 degrees -- gruntbert(LOTD)      <

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4
  2001-10-29 19:57 [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4 Jean-Noel GADREAU
  2001-10-30  3:09 ` Nils Juergens
@ 2001-10-30  9:46 ` Gaziz Nugmanov
  1 sibling, 0 replies; 4+ messages in thread
From: Gaziz Nugmanov @ 2001-10-30  9:46 UTC (permalink / raw)
  To: Jean-Noel GADREAU

Hello Jean-Noel,

I had similar problem so I cvs'ed latest lvm code and installed it.

It works much smoother for me now...

Hope that help.




Monday, October 29, 2001, 8:58:31 PM, you wrote:

JNG> Hi.

JNG> I have a problem to extend my current volume group "vg01". I did:

JNG> # pvcreate /dev/hde1 /dev/hde2
JNG> pvcreate -- physical volume "/dev/hde1" successfully created
JNG> pvcreate -- physical volume "/dev/hde2" successfully created

JNG> # vgextend -v vg01 /dev/hde1
JNG> vgextend -- locking logical volume manager
JNG> vgextend -- checking volume group name "vg01"
JNG> vgextend -- checking volume group "vg01" existence
JNG> vgextend -- checking for inactivity of volume group
JNG> vgextend -- reading data of volume group "vg01" from lvmtab
JNG> vgextend -- INFO: maximum logical volume size is 255.99 Gigabyte
JNG> vgextend -- reading data for all physical volumes from disk(s)
JNG> vgextend -- extending VGDA structures of volume group "vg01"
JNG> vgextend -- volume group "vg01" will be extended by 1 new physical volumes
JNG> vgextend -- extending volume group "vg01" by physical volume "/dev/hde1" 
JNG> in kernel
JNG> Segmentation fault (core dumped)

JNG> I am using RedHat 7.1 with a custom kernel to have LVM (2.4.9-6). I have 
JNG> 2 drives on this IDE controller (a Promise UltraDMA100DX2) and both work 
JNG> fine with linux. My secondary drive (/dev/hdf is already part of vg01).

JNG> I don't know if this is a bug or if I am not using this correctly. I 
JNG> could not find anything on the internet about this particular problem.

JNG> For more information, I am including the results of several commands. 
JNG> Let me know if you need more information.

JNG> Thanks in advance for your help.
JNG> Regards,
JNG> Jean-Noel GADREAU

JNG> ============================================

JNG> # vgdisplay -v vg01
JNG> --- Volume group ---
JNG> VG Name               vg01
JNG> VG Access             read/write
JNG> VG Status             available/resizable
JNG> VG #                  0
JNG> MAX LV                256
JNG> Cur LV                1
JNG> Open LV               1
JNG> MAX LV Size           255.99 GB
JNG> Max PV                256
JNG> Cur PV                1
JNG> Act PV                1
JNG> VG Size               37.27 GB
JNG> PE Size               4.00 MB
JNG> Total PE              9541
JNG> Alloc PE / Size       9500 / 37.11 GB
JNG> Free  PE / Size       41 / 164.00 MB
JNG> VG UUID               SCcP8o-73vj-4rCl-GbTx-A0up-5GAu-BEEgVL

JNG> --- Logical volume ---
JNG> LV Name                /dev/vg01/data
JNG> VG Name                vg01
JNG> LV Write Access        read/write
JNG> LV Status              available
JNG> LV #                   1
JNG> # open                 1
JNG> LV Size                37.11 GB
JNG> Current LE             9500
JNG> Allocated LE           9500
JNG> Allocation             next free
JNG> Read ahead sectors     120
JNG> Block device           58:0


JNG> --- Physical volumes ---
JNG> PV Name (#)           /dev/hdf1 (1)
JNG> PV Status             available / allocatable
JNG> Total PE / Free PE    9541 / 41

JNG> =============================================
JNG> # vgscan -v
JNG> vgscan -- removing "/etc/lvmtab" and "/etc/lvmtab.d"
JNG> vgscan -- creating empty "/etc/lvmtab" and "/etc/lvmtab.d"
JNG> vgscan -- reading all physical volumes (this may take a while...)
JNG> vgscan -- scanning for all active volume group(s) first
JNG> vgscan -- found active volume group "vg01"
JNG> vgscan -- reading data of volume group "vg01" from physical volume(s)
JNG> vgscan -- inserting "vg01" into lvmtab
JNG> vgscan -- backing up volume group "vg01"
JNG> vgscan -- checking volume group name "vg01"
JNG> vgscan -- checking volume group consistency of "vg01"
JNG> vgscan -- checking existence of "/etc/lvmtab.d"
JNG> vgscan -- storing volume group data of "vg01" in "/etc/lvmtab.d/vg01.tmp"
JNG> vgscan -- storing physical volume data of "vg01" in "/etc/lvmtab.d/vg01.tmp"
JNG> vgscan -- storing logical volume data of volume group "vg01" in 
JNG> "/etc/lvmtab.d/v
JNG> g01.tmp"
JNG> vgscan -- renaming "/etc/lvmtab.d/vg01.tmp" to "/etc/lvmtab.d/vg01"
JNG> vgscan -- removing special files and directory for volume group "vg01"
JNG> vgscan -- creating directory and group character special file for "vg01"
JNG> vgscan -- creating block device special files for vg01
JNG> vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
JNG> vgscan -- WARNING: This program does not do a VGDA backup of your volume 
JNG> group

JNG> =============================================
JNG> # pvscan -v
JNG> pvscan -- reading all physical volumes (this may take a while...)
JNG> pvscan -- walking through all physical volumes found
JNG> pvscan -- inactive PV "/dev/hde1" is in no VG  [18.64 GB]
JNG> pvscan -- inactive PV "/dev/hde2" is in no VG  [18.64 GB]
JNG> pvscan -- ACTIVE   PV "/dev/hdf1" of VG "vg01" [37.27 GB / 164.00 MB free]
JNG> pvscan -- total: 3 [74.56 GB] / in use: 1 [37.27 GB] / in no VG: 2 
JNG> [37.29 GB]





JNG> _______________________________________________
JNG> linux-lvm mailing list
JNG> linux-lvm@sistina.com
JNG> http://lists.sistina.com/mailman/listinfo/linux-lvm
JNG> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html



-- 
Best regards,
 Gaziz                            mailto:lvm@betta.gaziz.ca

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4
  2001-10-30  3:09 ` Nils Juergens
@ 2001-10-30 15:13   ` Jean-Noel GADREAU
  0 siblings, 0 replies; 4+ messages in thread
From: Jean-Noel GADREAU @ 2001-10-30 15:13 UTC (permalink / raw)
  To: linux-lvm

Nils Juergens wrote:

>On Mon, 29.10.01, Jean-Noel GADREAU <cathjn@gadreau.net> wrote:
>
>[snip]
>
>>vgextend -- extending volume group "vg01" by physical volume "/dev/hde1" 
>>in kernel
>>Segmentation fault (core dumped)
>>
>>I am using RedHat 7.1 with a custom kernel to have LVM (2.4.9-6). I have 
>>2 drives on this IDE controller (a Promise UltraDMA100DX2) and both work 
>>fine with linux. My secondary drive (/dev/hdf is already part of vg01).
>>
>[snip]
>
>The stock linux kernel comes with an old version of lvm. Please grab
>the latest version and make sure to patch your kernel (see
>PATCHES/README in the lvm distribution). You should also upgrade your
>userspace tools (lvcreate, vgextend and the like).
>
>On a further note, check which compiler you are using. gcc-2.96 should
>be used without optimization (-O0) and make sure you do not use
>gcc-3.0.x (it produces broken code on some occasions, this happened to
>me with the lvm tools).
>
>good luck,
>
>Nils
>
Thanks for your quick reply. I rebuilt the kernel but it did not work. 
However, recompiling without -O2 did it for me.

What I did (for those who might run into the same problem):

#cd LVM/1.0.1rc4
#./configure
 >>> here, edit make.tmpl to change CFLAGS=.... -O2 .... to CFLAGS=... 
-O0 ... <<<
#make
#make install

Thanks again for your time and quick answer.
Regards,
Jean-Noel

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2001-10-30 15:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-10-29 19:57 [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4 Jean-Noel GADREAU
2001-10-30  3:09 ` Nils Juergens
2001-10-30 15:13   ` Jean-Noel GADREAU
2001-10-30  9:46 ` Gaziz Nugmanov

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.