From: Heinz J. Mauelshagen <Heinz.Mauelshagen@t-online.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgextend segfaults
Date: Wed, 24 Jan 2001 19:28:58 +0000 [thread overview]
Message-ID: <20010124192858.A1295@srv.sistina.com> (raw)
In-Reply-To: <web-8135952@comned.com>; from wim@comned.com on Wed, Jan 24, 2001 at 03:35:30PM +0100
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-01-24 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 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=20010124192858.A1295@srv.sistina.com \
--to=heinz.mauelshagen@t-online.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;
as well as URLs for NNTP newsgroup(s).