From: Pierrick PONS <ppons@cvf.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] what's different between LVM 2 and LVM 1
Date: Fri Aug 30 04:25:02 2002 [thread overview]
Message-ID: <E17ki0Z-0007dJ-00@arwen.dev33.cvf> (raw)
In-Reply-To: Your message of "Fri, 30 Aug 2002 09:58:24 BST." <20020830085824.GA1090@fib011235813.fsnet.co.uk>
> On Fri, Aug 30, 2002 at 02:50:03PM +0800, lilha@legend.com.cn wrote:
> > I am puzzled what's different between LVM 2 and LVM 1
> > and I can't find any doc or introduction about the LVM2.
> >
> > who is kind to tell me what is LVM2,
> > and why i should use LVM2 replace of lvm1?
>
> LVM2 is the next version of LVM that has a couple of goals:
>
> i) A simpler more extensible kernel driver. This driver, called
> device-mapper, is already in the -ac series of 2.4 kernels. Hopefully
> device-mapper will replace the LVM1 driver completely in 2.[56].
>
> ii) Ability to more easily support the new features we want to put in.
> ATM we're concentrating on reproducing the functionality of LVM1,
> though a couple of new features (eg. writeable/fast snapshots) have
> crept in.
>
just a stupid question :
Why does LVM2 was not a version of lvm so that we just had to upgrade LVM ?
If LVM2 is just an upgrade of LVM1, why couldn't you continue with lvm-xxxxx ?
It should have been less confusing and easier to upgrade.
Sorry if it is abolutely stupid.
I'm using LVM1 and it works fine for me on a debian potato with a 2.4.18
kernel with hardware RAID5 . Thank you for your work.
Pierrick
next prev parent reply other threads:[~2002-08-30 4:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-30 1:51 [linux-lvm] what's different between LVM 2 and LVM 1 lilha
2002-08-30 3:59 ` Joe Thornber
2002-08-30 4:25 ` Pierrick PONS [this message]
2002-08-30 4:48 ` Joe Thornber
-- strict thread matches above, loose matches on Subject: below --
2002-09-01 21:41 lilha
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=E17ki0Z-0007dJ-00@arwen.dev33.cvf \
--to=ppons@cvf.fr \
--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