Linux LVM users
 help / color / mirror / Atom feed
From: AJ Lewis <lewis@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvcreate segfaults
Date: Thu, 6 Sep 2001 07:32:54 -0500	[thread overview]
Message-ID: <20010906073254.A10735@sistina.com> (raw)
In-Reply-To: <20010906090024.A373@btconnect.com>; from thornber@btconnect.com on Thu, Sep 06, 2001 at 09:00:25AM +0100

[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]

On Thu, Sep 06, 2001 at 09:00:25AM +0100, Joe Thornber wrote:
> On Wed, Sep 05, 2001 at 03:37:03PM -0500, AJ Lewis wrote:
> > On Wed, Sep 05, 2001 at 01:32:34PM -0500, John Marquart wrote:
> > > 	I am running LVM 1.0.1rc2 on  2.4.8 kernel ontop of a IBM
> > > Serverraid 4Mx RAID5 filesystem.  I am trying to create a new lv using
> > > "lvcreate -n foo -L 4M rootvg" - however that command insists on giving me
> > > a segfault.  
> > 
> > Here is a patch that should fix this problem.  It has already been applied
> > to the CVS.  just save this to a file and apply it to the 1.0.1-rc2 source
> > with the -p0 flag after cd'ing to the 1.0.1-rc2 directory.
> 
> I don't think this patch fixes it, it's just a tidy up.

Hmm...was looking at this:
http://lists.sistina.com/pipermail/lvm-devel/2001-September/000637.html

Sounded like changing the inlines fixed the seg-fault for this guy.  

John,
you could also try the patch referred to from that e-mail, but it doesn't
sound like it's the same problem i guess...

Regards,
-- 
AJ Lewis
Sistina Software Inc.                  Voice:  612-638-0500
1313 5th St SE, Suite 111              Fax:    612-638-0500
Minneapolis, MN 55414                  E-Mail: lewis@sistina.com
http://www.sistina.com

Current GPG fingerprint = 60F3 160D C0D5 2C4B 751B  4FF9 6F67 E9BC 44CD DE95

-----Begin Obligatory Humorous Quote----------------------------------------
Programming graphics in X is like finding sqrt(pi) using Roman numerals.
-----End Obligatory Humorous Quote------------------------------------------

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-09-06 12:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05  9:33 [linux-lvm] LV size maximum Jan-Benedict Glaw
2001-09-05  9:53 ` svetljo
2001-09-05 10:09   ` Jan-Benedict Glaw
2001-09-05 10:38     ` svetljo
2001-09-05 10:24 ` Ragnar Kjørstad
2001-09-05 18:11   ` Andreas Dilger
2001-09-05 18:32     ` [linux-lvm] lvcreate segfaults John Marquart
2001-09-05 18:57       ` John Marquart
2001-09-05 20:37       ` AJ Lewis
2001-09-05 22:42         ` John Marquart
2001-09-06  8:00         ` Joe Thornber
2001-09-06 12:32           ` AJ Lewis [this message]
2001-09-07 16:05             ` John Marquart
2001-09-10 16:08               ` AJ Lewis
  -- strict thread matches above, loose matches on Subject: below --
2001-09-07 15:59 Robert_Macaulay
2001-09-07 16:17 ` Benjamin Reed

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=20010906073254.A10735@sistina.com \
    --to=lewis@sistina.com \
    --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