From: lewis@sistina.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Once again ... Kernel 2.4.0 - What can I do ?
Date: Mon, 8 Jan 2001 09:49:02 -0600 [thread overview]
Message-ID: <20010108094902.A30177@sistina.com> (raw)
In-Reply-To: <1504018708.20010108141026@lzer.net>; from jan.w@lzer.net on Mon, Jan 08, 2001 at 02:10:26PM +0100
[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]
On Mon, Jan 08, 2001 at 02:10:26PM +0100, Jan Walzer wrote:
> I'm currently using Kernel 2.4.0-test10 with LVM 0.8final ...
> I have a 55Gig LVM-Partition (with reiserfs) and no backup ....
> (Yes I know, but there's no money for a poor student to backup ...)
>
> Now I want to use the final 2.4.0 and it is now a fact, that there
> is v0.9 in it. (why it is, is another question...)
>
> I ask now, what I can do ...
> It seems that they both are not compatible, as the vgscan under
> 2.4.0fin brings me a protocol error ...
Look through the linux-lvm mailing list archives for the message with the
subject line "[linux-lvm] Clarification concerning the status of LVM and 2.4".
This attempts to explain what is currently going on with LVM and the 2.4.x
linux kernel
> Is there a way to "downpatch" the kernel to lvm0.8 ???
> or better:
> can I convert the volume to 0.9 without data-loss ???
If you are truly worried about your data, stay with 0.8final and do not
upgrade your kernel for the moment. The LVM team is evaluating the release of
a 0.8final backpatch for 2.4.0, but we obviously want to test this before we
release it to folks like yourselves that have data they don't want to lose.
> Thanx in advance ... Jan
>
> PS: Please don't tell me all the reasons, why I need a backup.
> I know it myself, but there is at the moment no way ....
We cannot in any way, shape, or form guarantee the integrity of your data. If
you choose run without backup, that is up to you.
Regards,
--
AJ Lewis
Sistina Software Inc. Voice: 612-379-3951
1313 5th St SE, Suite 111 Fax: 612-379-3952
Minneapolis, MN 55414 E-Mail: lewis@sistina.com
http://www.sistina.com
Current GPG fingerprint = 3B5F 6011 5216 76A5 2F6B 52A0 941E 1261 0029 2648
Get my key at: http://www.sistina.com/~lewis/gpgkey
(Unfortunately, the PKS-type keyservers do not work with multiple sub-keys)
-----Begin Obligatory Humorous Quote----------------------------------------
Hey! It compiles! Ship it!
-----End Obligatory Humorous Quote------------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-01-08 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 13:10 [linux-lvm] Once again ... Kernel 2.4.0 - What can I do ? Jan Walzer
2001-01-08 15:49 ` lewis [this message]
2001-01-08 16:52 ` Paul Jakma
2001-01-08 23:40 ` Claudio Matsuoka
2001-01-08 23:52 ` Jan Niehusmann
2001-01-10 19:34 ` Christoph Hellwig
2001-01-10 22:33 ` [linux-lvm] Learning how LVM work Simone Morellato
2001-01-11 9:13 ` 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=20010108094902.A30177@sistina.com \
--to=lewis@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.