All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: [lvm-devel] [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Thu Jan 31 05:31:01 2002	[thread overview]
Message-ID: <20020131122624.C9764@sistina.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10201302234340.19357-100000@pzat.meep.org>; from oolon@ankh.org on Wed, Jan 30, 2002 at 10:36:10PM +0000

On Wed, Jan 30, 2002 at 10:36:10PM +0000, James Hawtin wrote:
> Licencing is important to me, too. Also is it pv/lv compatible with lvm 1
> or is it system rebuild time.....

LVM2 supports the existing LVM1 on disk metadata format and will support another
so called format2 soon which has enhanced metadata redundancy and transaction 
oriented updates in order to largely reduce the likelyhood of inacessable
VGs and metadata restores.

IOW: it will make LVM more insensible to hardware flaws.


> 
> James
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-01-31  5:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 14:23 [linux-lvm] [ANNOUNCE] LVM reimplementation ready for beta testing Joe Thornber
2002-01-30 20:22 ` Joe Thornber
2002-01-30 15:54 ` [linux-lvm] Re: [lvm-devel] " Andreas Dilger
2002-01-30 21:54   ` Andreas Dilger
2002-01-30 16:05   ` [linux-lvm] " Jim McDonald
2002-01-30 22:03     ` Jim McDonald
2002-01-30 18:15     ` [linux-lvm] " Lars Kellogg-Stedman
2002-01-31  3:00     ` [linux-lvm] Re: [lvm-devel] " Joe Thornber
2002-01-30 16:37   ` James Hawtin
2002-01-31  5:31     ` Heinz J . Mauelshagen [this message]
2002-01-30 23:09   ` Joe Thornber
2002-01-31  3:08     ` [linux-lvm] " Joe Thornber
2002-01-30 19:48 ` [linux-lvm] " Daniel Phillips
2002-01-31  1:53   ` Daniel Phillips
2002-01-31  6:30   ` [linux-lvm] " Heinz J . Mauelshagen
2002-01-31  1:01 ` christophe barbé
2002-01-31 12:45   ` Heinz J . Mauelshagen
2002-01-31 18:42     ` Jeff Garzik
2002-02-01  9:03       ` Heinz J . Mauelshagen
2002-02-04 22:16         ` Bill Davidsen
2002-02-05 10:18           ` Heinz J . Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 13:54 [linux-lvm] Re: [lvm-devel] " Steve Pratt
2002-01-31 19:52 ` Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01  3:47   ` Joe Thornber

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=20020131122624.C9764@sistina.com \
    --to=mauelshagen@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 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.