From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM question on move and resize
Date: Fri, 14 Jul 2006 18:43:02 +0200 [thread overview]
Message-ID: <44B7C996.8030307@conterra.de> (raw)
In-Reply-To: <20060714151524.37351.qmail@web50702.mail.yahoo.com>
John Koshi wrote:
> Actually I do have a large USB disk (Seagate 160GB)
> and had considered using it during this expansion of
> the Linux installation. I'm interested in seeing your
> solution, in this case.
Hi John,
i frequently reorganized my data by extending my VG by
a new disk (vgextend) and moved all data off the unwanted
disk using "vgmove". Afterwards I may unplug the unwanted disk
from my VG (vgreduce). All this may be performed, while people
are working on this server! But I'm using hot-plugable
SATA disks on a raid controller.
But you talk about a laptop and an USB disk, and the device to
replace is an extended partition, not a hot pluggable SATA disk.
So I think there are too much traps in your case to fail.
Instead I would simply install a plain ext2 partition on the
USB disk, mount it and copy all data using simple "cp -a" to
the USB disk. Then erase hda4 and recreate it as a plain primary
partition, install LVM again and copy the data back. This is
not as fancy as using LVM, but much saver in your case.
After all I even think: it may be currently ugly, but it works.
So may be you should keep this setup until you really need
to change it.
regards, Dieter.
prev parent reply other threads:[~2006-07-14 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 1:24 [linux-lvm] LVM question on move and resize John Koshi
2006-07-13 8:35 ` Dieter Stüken
2006-07-13 18:22 ` John Koshi
2006-07-14 11:00 ` Dieter Stüken
2006-07-14 15:15 ` John Koshi
2006-07-14 16:43 ` Dieter Stüken [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=44B7C996.8030307@conterra.de \
--to=stueken@conterra.de \
--cc=linux-lvm@redhat.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).