All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] RAID and LVM?
Date: Tue, 27 Jul 1999 11:47:37 +0200	[thread overview]
Message-ID: <19990727114737.E8908@colombina.comedia.it> (raw)
In-Reply-To: <Pine.LNX.3.96.990726222206.21028A-100000@chiara.csoma.elte.hu>; from Ingo Molnar on Mon, Jul 26, 1999 at 10:25:50PM +0200

On Mon, Jul 26, 1999 at 10:25:50PM +0200, Ingo Molnar wrote:
> (rather flame me for it ;) The new RAID driver will likely not go into
> 2.2.11, but into 2.2.12. Anyway, the new RAID 0723 release is much more
> merging-friendly wrt. LVM.

ok, you asked for it ;)
there is still some idiosyncrasye wrt HSM and it doesn't build.
*joking*
2.2.11 or 2.2.12 does not seem to be a big problem to me.

> > or ideally for raid to be fully integrated into LVM, and create
> > RAID-5 VG's. 
> or, considering the relative complexity of the two drivers (and the
> conceptual background), to integrate LVM into the concepts of RAID :) Or
i dont understand your last sentence
> let them live side by side as now.

i believe useful integrating raid and lvm
it means a user can dcide the different raid policy
for each type of data.
eg. striping for /var/spool/junk
3 way raid1 for /very/important/stuff
raid5 for /other/data

Leaving things as now is still very useful, and i will be very 
happy to have this arrangement finalized.
we really need to fix LILO (or another boot loader, grub already
can read ext2 filesystems) to be able to understand raid and lvm.

as a side question, how does LVM autodetect works
(if it exists, that is)?

Regards
Luca

-- 
Luca Berra -- bluca@comedia.it
    Communications Media & Services S.r.l.

  parent reply	other threads:[~1999-07-27  9:47 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 [this message]
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
1999-08-02 15:37                         ` Luca Berra
1999-08-02 16:12                         ` S. Ryan Quick
1999-08-02 19:21                         ` Paul Jakma
  -- strict thread matches above, loose matches on Subject: below --
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=19990727114737.E8908@colombina.comedia.it \
    --to=bluca@comedia.it \
    --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.