From: Russell Coker <bofh@coker.com.au>
To: linux-lvm@sistina.com,
Torsten Landschoff <torsten@pclab.ifg.uni-kiel.de>
Subject: Re: [linux-lvm] Upgrade path from 0.8i to 0.9?
Date: Sun, 17 Dec 2000 09:40:56 +0100 [thread overview]
Message-ID: <0012170940560K.00774@lyta> (raw)
In-Reply-To: <20001216184849.A12569@pclab.ifg.uni-kiel.de>
On Saturday 16 December 2000 18:48, Torsten Landschoff wrote:
> We are planning to upgrade a production server tomorrow. As we have to
> build a new kernel anyway I would like to upgrade the LVM code from 0.8i
> to 0.9.
>
> I just tried the same thing on a test system and I was unable to get it
> working. After installing the new kernel I installed the lvm Debian
> package from sistina.com (which removed /etc/lvmtab and /etc/lvmtab.d)
> and tried to reactivate the volumes. This is what I get:
I should have this sort of thing working cleanly from the Debian packaging
part within 2 weeks. This includes having /etc/lvmtab and /etc/lvmtab.d
owned by the lvm-common package which won't need to be upgraded (except for
when man pages change). Also upgrading lvm-common won't trash things because
they will be registered as conffiles.
Please try out my test packages of 0.8.1 on http://www.coker.com.au/lvm/ on a
test machine (NOT A PRODUCTION SERVER) and let me know how they go.
--
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/projects.html Projects I am working on
http://www.coker.com.au/~russell/ My home page
prev parent reply other threads:[~2000-12-17 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-16 17:48 [linux-lvm] Upgrade path from 0.8i to 0.9? Torsten Landschoff
2000-12-17 8:40 ` Russell Coker [this message]
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=0012170940560K.00774@lyta \
--to=bofh@coker.com.au \
--cc=linux-lvm@sistina.com \
--cc=torsten@pclab.ifg.uni-kiel.de \
/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