From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: Re: [linux-lvm] Installing LVM on s/390 redhat 7.2 2.4.7-39
Date: Thu Jan 30 06:05:02 2003 [thread overview]
Message-ID: <20030130120456.GJ802@tykepenguin.com> (raw)
In-Reply-To: <20030130115503.LFHJ14589.mta02-svc.ntlworld.com@[10.137.100.62]>
On Thu, Jan 30, 2003 at 11:55:03AM +0000, jrelist@ntlworld.com wrote:
>
> Well, it's kind of working now ! I followed the link, got the patch. I patched lvm 1.0.6 to my kernel, ended up having to manually change lvm-snap.c, went throught the build and IPL'd successfully !
>
> However, I'm now faced with another problem. After creating, then extending a VG, a subsequent vgscan gives 'segmentation error' and a pvscan now says the vg the devices are connected to is unknown. The rpm installed for the lvm utilities is 1.0.3-10, and from searching the lists I believe I need an updated version of VGSCAN. I know there won't be a binary available for s/390 redhat at 1.0.6 level, but I'd like to what would be the best SRPMS to get - I've seen a couple of different versions but nothing specifically mentioned as for a Redhat distro.
>
> Thanks for your help so far, nearly there.... !
>
I don't think there are any SRPMS (not official ones anyway), but the tar.gz
sources should build just fine.
--
patrick
next prev parent reply other threads:[~2003-01-30 6:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 5:56 Re: [linux-lvm] Installing LVM on s/390 redhat 7.2 2.4.7-39 jrelist
2003-01-30 6:05 ` Patrick Caulfield [this message]
2003-01-30 11:04 ` Peter A. Castro
-- strict thread matches above, loose matches on Subject: below --
2003-01-30 12:23 jrelist
2003-01-29 4:31 jrelist
2003-01-28 5:09 jrelist
2003-01-28 5:20 ` Patrick Caulfield
2003-01-28 18:58 ` Peter A. Castro
2003-01-27 7:05 jrelist
2003-01-23 16:00 jrelist
2003-01-23 18:35 ` Peter A. Castro
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=20030130120456.GJ802@tykepenguin.com \
--to=caulfield@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