From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Feature : Merge two LV
Date: Thu, 06 Sep 2001 18:14:12 -0500 [thread overview]
Message-ID: <12570000.999818052@dizzy> (raw)
In-Reply-To: <20010906220553.Z32553@turbolinux.com>
-- Andreas Dilger <adilger@turbolabs.com>
> On Sep 06, 2001 21:51 +0200, Henk Birkholz wrote:
>> It would have been easier (without moving the date manually) if some kind
>> of lvmerge would exist, which would merge the lv and thier fs
>> automatically. Maybe there is ia wayto do it, i simply don't know.
>> In that case i would be glad to know that way from you. (and be added to
>> you FAQ).
>
> What you ask for is very complex. It is not so much an issue of LVM
> (which could do such a thing relatively easily), but a filesystem issue
> (which is _very_ hard to do. Even with a tree-based filesystem like
> reiserfs or XFS, there are all sorts of duplicate identifiers stored in
> the filesystem, like block numbers, inode numbers, etc, which would make
> it complex to resolve.
lvcreate -l somesize vgXX;
mkfs.ext2 -b4096 -i10240 /dev/vgXX/lvolY;
mount /dev/vgXX/lvolY /mnt;
find /lvolA/mount/point /lvolB/mount/point -xdev | cpio -pd --dot /mnt;
vi /etc/fstab;
<remove lvolA and lvolB, add in lvolY>
umount /mnt;
mount -a;
If at this point you have what you want then lvremove lvolA & lvolB.
Nice thing about it is that nothing gets removed until the new file
system looks clean.
If you're tight on space create a smaller volume, archive onto it
instead of tape w/ bzip2 -9 (i.e., seriously squish the data), blow
off the lvol's and recover from disk.
--
Steven Lembark 2930 W. Palmer
Workhorse Computing Chicago, IL 60647
+1 800 762 1582
prev parent reply other threads:[~2001-09-06 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 19:51 [linux-lvm] Feature : Merge two LV Henk Birkholz
2001-09-07 4:05 ` Andreas Dilger
2001-09-06 23:14 ` Steven Lembark [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=12570000.999818052@dizzy \
--to=lembark@wrkhors.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.