All of lore.kernel.org
 help / color / mirror / Atom feed
From: John DeFranco <defranco@cup.hp.com>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM on 2.2.17 (again)
Date: Tue, 26 Sep 2000 15:07:06 -0700	[thread overview]
Message-ID: <39D11E0A.18E83DA2@cup.hp.com> (raw)
In-Reply-To: 200009260151.e8Q1pdw19220@webber.adilger.net

Thanks! That helped alot. One other question,
I wanted to pvcreate a software RAID device
(/dev/md0 in this case). This is a simple two
disk mirror (since LVM does not do mirroring).
It would not let me do this however. The FAQ
seems to indicate that I can (at least that
the way I am interpreting the last section: 

  I recommend to use dedicated hardware RAID 
  subsystems or Multiple Devices to have the 
  redundancy below the LVM. In this case you 
  just don't care about Logical Volume data 
  redundancy and you don't run into the 
  dangerous situation that your data is 
  not redundant by accident.
).

Does anyone know if this is possible and if so how
to accomplish it?

Thanks! 

Andreas Dilger wrote:
> 
> John DeFranco writes:
> > I've checked the LVM email archives so I know there has
> > been lots of discussions on how to get LVM to work on
> > 2.2.17, but unfortunately I'm having problems just
> > building the kernel. I started with Turbolinux Server
> > 6.0.2 (which is 2.2.14) and then added the 2.2.15-2.2.17
> > patches. When I build I get:
> >
> > lvm-snap.c:28: linux/iobuf.h: No such file or directory
> > lvm-snap.c: In function `lvm_snapshot_COW':
> > lvm-snap.c:253: dereferencing pointer to incomplete type
> > lvm-snap.c:257: warning: implicit declaration of function
> > `brw_kiovec'
> > lvm-snap.c: In function `lvm_snapshot_alloc_iobuf_pages':
> > lvm-snap.c:308: warning: implicit declaration of function
> > `expand_kiobuf'
> 
> Are you using my 2.2 patches (which is a backport of 0.8final from 2.4)?
> In this case you need to also apply the RAWIO patches available at
> Stephen Tweedie's site  ftp://ftp.linux.org.uk/pub/linux/sct/
> Alternately, if you don't need/want LVM snapshots, you can delete lvm-snap.c,
> and delete the references in lvm.c to any "snap" functions, etc.  There
> are about half a dozen places where this happens.  If I get around to
> it, I will update my patch to simplify turning off lvm snapshots...
> 
> Cheers, Andreas
> --
> Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>                  \  would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

-- 
==========
Cheers
   -jdf

  reply	other threads:[~2000-09-26 22:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-25 20:43 [linux-lvm] LVM on 2.2.17 (again) John DeFranco
2000-09-26  1:51 ` Andreas Dilger
2000-09-26 22:07   ` John DeFranco [this message]
2000-09-28 16:55     ` John DeFranco
  -- strict thread matches above, loose matches on Subject: below --
2000-09-27  3:01 S. Michael Denton

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=39D11E0A.18E83DA2@cup.hp.com \
    --to=defranco@cup.hp.com \
    --cc=adilger@turbolinux.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.