From: Benoit SERRA <bs@infologic.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM
Date: Wed, 24 Jan 2001 13:48:47 +0100 [thread overview]
Message-ID: <3A6ECF2F.87A006EF@infologic.fr> (raw)
In-Reply-To: OF48A10ED6.E78FC82F-ONC12569DE.00339875@icos.be
dirk.derycke@icos.be wrote:
>
> Hi all,
>
> for me the upgrade from 2.4.0-test12 to 2.4.0 was simple. I upgraded the
> user tools to 0.9
> rebooted with 2.4.0. Important note: my root partition is NOT LVM.
> Then I executed the vgscan from the 0.9 tools which detected the 0.8 LVM
> data, then I activated the volume group and mounted the LV's.
>
> A backup however is always a safe thing to do. But normally the above
> procedure should work fine...
> Note that I had a 2.2.14 with 0.7 tools first before 2.4.0-testXX and
> didn't have to backup and restore data...
>
> What would be the point of having industrial strength disk management when
> you have to backup and restore
> every software upgrade (imagine hundreds of gigs)?.
>
> regards,
>
> Dirk
>
I'm not sure that playing with version of critical software layers such
as LVM is a good idea if you value your data.
My experience say that you should make a backup of your data before
trying to upgrade to 0.9, but I'm parano�d.
next prev parent reply other threads:[~2001-01-24 12:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 9:30 [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM dirk.derycke
2001-01-24 12:48 ` Benoit SERRA [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 8:18 Mark Phillips
2001-01-24 8:31 ` Benoit SERRA
2001-01-24 11:02 ` Jan Niehusmann
[not found] ` <20010124040016.A30469@jhereg.dmeyer.net>
2001-01-24 9:05 ` Mark Phillips
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=3A6ECF2F.87A006EF@infologic.fr \
--to=bs@infologic.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;
as well as URLs for NNTP newsgroup(s).