From: Andreas Dilger <adilger@turbolabs.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Feature : Merge two LV
Date: Thu, 6 Sep 2001 22:05:53 -0600 [thread overview]
Message-ID: <20010906220553.Z32553@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0109062137150.11080-100000@x14.informatik.uni-bremen.de>
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.
You are far better off just to do (assuming you collapse /usr/local into /usr):
umount /usr/local
e2fsadm -L -(free space) /dev/vg/lvusrlocal # if needed, assuming ext2/ext3
e2fsadm -L +(needed space) /dev/vg/lvusr # if needed, assuming ext2/ext3
mount /dev/vg/lvusrlocal /mnt/tmp
tar cf - -C /mnt/tmp . | tar xf - -C /usr/local
umount /mnt/tmp
lvremove /dev/vg/lvusrlocal
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-07 4:05 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 [this message]
2001-09-06 23:14 ` Steven Lembark
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=20010906220553.Z32553@turbolinux.com \
--to=adilger@turbolabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox