Linux LVM users
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: linux-lvm@msede.com
Subject: [linux-lvm] Re: Problems with 0.8pre tools (fwd)
Date: Thu, 03 Feb 2000 13:36:03 +0100	[thread overview]
Message-ID: <38997633.6D7376C3@msede.com> (raw)

Forwarded message ...

-------- Original Message --------
Date: Wed, 2 Feb 2000 23:51:40 -0500 (EST)
From: Jim Cain <me@jimcain.net>
Subject: Re: Problems with 0.8pre tools

On Wed, 2 Feb 2000, Jim Cain wrote:

> All,
> 
> I had some problems getting the tools to build. First, in
> tools/lib/liblvm.h, the included file <linux/lvm.h> did not compile
> because the reference to spinlock_t on line 573 was unknown. I added an
> #include <linux/spinlock.h> to liblvm.h, and everything in the lib
> directory built fine.
> 
> Next, in tools/lvmchange.c on line 160, the identifier LVM_RESET was
> unknown. This is defined in <linux/lvm.h>, but only if LVM_TOTAL_RESET is
> defined. I removed the #ifdef around it so that LVM_RESET is always
> defined. After that change, the tools built okay.
> 
> Well, not completely okay. Because when I do the following:
> 
> pvcreate /dev/hd[bc]1
> vgcreate vg01 /dev/hd[bc]1
> 
> the vgcreate command dumps core on a segmentation fault. I'm wondering if
> any of the fixes I made were incomplete or the wrong way to fix it.
> 
> This is being built on kernel 2.3.40 with the 0.8i patch.

I should have also mentioned that I made the changes to
tools/lib/lvm_tab_vg_check_exist_all_vg.c that Heinz describes in his
message on Jan. 1. I get no output from vgcreate at all, just the seg
fault.

Cheers,
Jim

                 reply	other threads:[~2000-02-03 12:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=38997633.6D7376C3@msede.com \
    --to=mike@msede.com \
    --cc=linux-lvm@msede.com \
    --cc=me@jimcain.net \
    /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