From: Jan Niehusmann <list039@gondor.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Once again ... Kernel 2.4.0 - What can I do ?
Date: Tue, 9 Jan 2001 00:52:28 +0100 [thread overview]
Message-ID: <20010109005228.A7379@gondor.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101082133180.32197-100000@scuzzlebutt.helllabs>; from claudio@conectiva.com on Mon, Jan 08, 2001 at 09:40:55PM -0200
On Mon, Jan 08, 2001 at 09:40:55PM -0200, Claudio Matsuoka wrote:
> > can I convert the volume to 0.9 without data-loss ???
>
> The on-disk data structures are compatible, you only need a set of
> userspace tools with the same IOP as the kernel.
Well, sort of. When I actually tried it out, I got an error message
from LVM 0.8.1's vgscan:
vgscan -- ERROR "lvm_remouverecursive(): opendir" removing volume group director
y and special files
vgscan -- ERROR "lvm_remouverecursive(): opendir" creating "/etc/lvmtab" and "/e
tc/lvmtab.d"
vgscan -d showed me an interesting thing:
<4444> vg_check_name -- vg_name: "5HozPsvN3ueT3iLNQpeAE08HISKPy1O7"
First I thought that bogous vg_name may be caused by data corruption, until
I noticed that the string above is 0.9's uuid of that VG.
I didn't try to fix the bug as 0.9 is fine for me.
The above happend with some random -testxx-preyy kernel, so it may be
caused by something completely different. I'm just not as sure as I was
before that going back from 0.9 to 0.8 is possibly without any problems.
Jan
next prev parent reply other threads:[~2001-01-08 23:52 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
2001-01-08 16:52 ` Paul Jakma
2001-01-08 23:40 ` Claudio Matsuoka
2001-01-08 23:52 ` Jan Niehusmann [this message]
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=20010109005228.A7379@gondor.com \
--to=list039@gondor.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.