linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: James Pattinson <jamesp@aethos.co.uk>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] RAID and LVM?
Date: Mon, 2 Aug 1999 14:25:09 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.10.9908021419460.1912-100000@fuse.aethos.co.uk> (raw)
In-Reply-To: <19990802150301.B20900@colombina.comedia.it>

Cheers - I'll try that later on.

Does anyone have a such thing as a patch against 2.2.10 which includes LVM
and RAID0145? It's just I feel a lot happier running 2.2.10, rather than
-ac12 - as it breaks a few things on my notebook. And yes - I do run lvm
and raid regularly on this, as well and informix dynamic server.
/dev/loop* is my friend!

James

PS - I tried devfs on -ac12 last week as well, impressive, but I couldn't
seem to use my SCSI cdrom drive anymore, no such thing as /dev/scd or even
/dev/*cd* exists! Also, I had to `modprobe loop` before I could access
/dev/loop*.

On Mon, 2 Aug 1999, Luca Berra wrote:

> On Mon, Aug 02, 1999 at 09:57:24AM +0100, James Pattinson wrote:
> > Is anyone using alan's ac12 patch for RAID and LVM? My machine at home has
> > 2.2.10 with raid0145 applied, and my root partition is striped across two
> > hd/s controllers. I want to be able to use LVM though.
> i did test it, it seems working, unluckyly ac12 breaks isdn, so i cannot use
> it much on my main machine :(
> 
> > I downloaded alan's patch, but then couldn't get LVM tools to compile at
> > all. Do I need to upgrade to a new glibc or something? I'm running more or
> > less a basic RH6 system.
> 
> you need this patch to build raidtools:
> http://www.comedia.it/bluca/lvm/lvm-0.7.glibc.patch
> (also attached here)
> if you need i can also provide a spec file
> or source RPM
> 
> 
> -- 
> Luca Berra -- bluca@comedia.it
>     Communications Media & Services S.r.l.
> 

  reply	other threads:[~1999-08-02 13:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-14 22:38 [linux-lvm] RAID and LVM? Paul Jakma
1999-07-14 23:04 ` Heinz Mauelshagen
1999-07-14 23:15   ` Paul Jakma
1999-07-20 21:40   ` Paul Jakma
1999-07-21 20:49     ` Luca Berra
1999-07-21 21:22       ` Paul Jakma
1999-07-22  7:48         ` Luca Berra
1999-07-25 22:29           ` Luca Berra
1999-07-26  0:12             ` Paul Jakma
1999-07-26 11:11               ` Luca Berra
1999-07-26 18:54                 ` Paul Jakma
1999-07-26 20:25                   ` Ingo Molnar
1999-07-26 20:52                     ` Paul Jakma
1999-07-27  9:47                     ` Luca Berra
1999-07-28  9:31                       ` Luca Berra
1999-08-02  8:57                   ` James Pattinson
1999-08-02 13:03                     ` Luca Berra
1999-08-02 13:25                       ` James Pattinson [this message]
1999-08-02 15:37                         ` Luca Berra
1999-08-02 16:12                         ` S. Ryan Quick
1999-08-02 19:21                         ` Paul Jakma
1999-07-27 12:23 Heinz Mauelshagen
1999-07-27 12:57 ` Luca Berra
1999-07-27 15:37 Heinz Mauelshagen
     [not found] <852567BA.0076DBF1.00@USCOMM02.aholdusa.com>
1999-08-03 20:24 ` Paul Jakma

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=Pine.LNX.4.10.9908021419460.1912-100000@fuse.aethos.co.uk \
    --to=jamesp@aethos.co.uk \
    --cc=linux-lvm@msede.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).