From: Jean-Noel GADREAU <cathjn@gadreau.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Segmentation Fault with vgextend and LVM 1.0.1rc4
Date: Tue Oct 30 15:13:02 2001 [thread overview]
Message-ID: <3BDF1851.2030803@gadreau.net> (raw)
In-Reply-To: 20011030101059.A1138@guldukat.muon.local
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
next prev parent reply other threads:[~2001-10-30 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-10-30 9:46 ` Gaziz Nugmanov
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=3BDF1851.2030803@gadreau.net \
--to=cathjn@gadreau.net \
--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.