From: Friedrich Lobenstock <fl@fl.priv.at>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] lvm 0.8 to 1.0 transition?
Date: Wed Feb 27 07:38:02 2002 [thread overview]
Message-ID: <3C7CE18F.BCFDDD7B@fl.priv.at> (raw)
In-Reply-To: 20020227102700.C19249@sistina.com
"Heinz J . Mauelshagen" wrote:
>
> In case you just want to update your LVM software, you don't need to
> vgexport/vgimport your VGs as described under that URL.
>
> Presuming that you took backups of your data and metadata (/etc/lvmconf/*)
> and don't have root on a LV,
Yes root is on a LV on RAID1 and the data is on a LV on another RAID1
# uname -a
Linux www 2.4.0-test12-pre4-reiserfs-md-fixes #4 Fri Jan 19 14:48:29 CET 2001 i686 unknown
# cat /proc/lvm
LVM driver version 0.8final (15/02/2000)
Total: 2 VGs 2 PVs 6 LVs (6 LVs open 6 times)
Global: 156410 bytes malloced IOP version: 6 22:43:33 active
VG: system-disk [1 PV, 4 LV/4 open] PE Size: 4096 KB
Usage [KB/PE]: 9969664 /2434 total 9969664 /2434 used 0 /0 free
PV: [AA] md1 9969664 /2434 9969664 /2434 0 /0
LVs: [AWCL ] swap 524288 /128 1x open
[AWDL ] root 2097152 /512 1x open
[AWDL ] tmp 524288 /128 1x open
[AWDL ] var 6823936 /1666 1x open
VG: data-disk [1 PV, 2 LV/2 open] PE Size: 8192 KB
Usage [KB/PE]: 78143488 /9539 total 55615488 /6789 used 22528000 /2750 free
PV: [AA] md3 78143488 /9539 55615488 /6789 22528000 /2750
LVs: [AWDL ] 1 18022400 /2200 1x open
[AWDL ] 2 37593088 /4589 1x open
# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/system-disk/root
2.0G 1.5G 522M 75% /
/dev/md0 50M 37M 13M 74% /boot
/dev/system-disk/tmp 512M 32M 480M 6% /tmp
/dev/system-disk/var 6.5G 92M 6.4G 1% /var
/dev/data-disk/1 17G 12G 5.1G 70% /mount/1
/dev/data-disk/2 36G 12G 24G 34% /mount/2
/dev/system-disk/ has PV /dev/md1
/dev/data-disk/ has PV /dev/md3
# cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hdc1[0] hda1[1]
51264 blocks [2/2] [UU]
md1 : active raid1 hdc2[0] hda2[1]
9970560 blocks [2/2] [UU]
md3 : active raid1 hdg1[1] hde1[0]
78150592 blocks [2/2] [UU]
Therefore I will install a new system and I'll just take the disks
that belong to /dev/md3 and put them in this new system. So I'll
have the old system to put the disks back if anything goes wrong
in the new system.
In the new system I just need to pvmove the the data onto the new
disks, this time hardware RAID instead of software RAID, so no
fancy stuff to get lilo boot with root on LV.
So how should I do it, just "vgscan;vgchange -ay" or do I need to
vgexport/vgimport and will this cause troubles?
--
MfG / Regards
Friedrich Lobenstock
\x7f
next prev parent reply other threads:[~2002-02-27 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 11:45 [linux-lvm] lvm 0.8 to 1.0 transition? Friedrich Lobenstock
2002-02-27 3:27 ` Heinz J . Mauelshagen
2002-02-27 7:38 ` Friedrich Lobenstock [this message]
2002-02-27 11:43 ` Heinz J . Mauelshagen
2002-02-27 14:25 ` Friedrich Lobenstock
2002-02-27 16:12 ` Heinz J . Mauelshagen
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=3C7CE18F.BCFDDD7B@fl.priv.at \
--to=fl@fl.priv.at \
--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