From: Rupert Heesom <raheesom@navpoint.com>
To: linux-lvm@sistina.com
Subject: RE: [linux-lvm] Converting my Root file system to LVM
Date: 22 May 2001 19:53:57 -0400 [thread overview]
Message-ID: <990575643.1151.0.camel@localhost> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJIEMHIOAA.steve.wray@the.net.nz>
Many thanks for the 2 replies!
Well, since I had the same problem as Steve, I implemented his solution.
Tnx, Steve for the easy howto of your's below.
BTW, what on earth is that "mount -o loop" command?
As I tap on my keyboard, I am working inside of my new LVol, so it
worked, guys!
Since my LVol is on my 2nd disk, next, I think I'll try extending my
Lvol back to cover my 1st disk as well.
One more bit of help, if you can? -
I want to pvmove the file contents of my 2nd disk (/dev/sdb) to my 1st
disk (/dev/sda). My 1st disk is nice & quiet! Now the lvm-howto
specifies my next step (adding the "old partition" into the Lvol) as --
pvcreate /dev/sda <using my device names>
vgextend vg /dev/sda
--- Seeing as I want to do a pvmove of data from /dev/sdb to /dev/sda,
when would I do the pvmove? As I understand LVM, I need to have the PV
created and integrated into the VG before I can use pvmove - is this
correct? Then, once pvmove is used, I can then extend the LV & file
system to cover both PVs using e2fsadm, right?
On 23 May 2001 10:56:39 +1200, Steve Wray wrote:
> AHA!
> you too, huh?
> You'll have to add sed to the initial ramdisk.
>
> Its in /boot/initrd<something>.gz
> unzip it and mount it with
> mount -o loop /boot/initrd<something> /mnt/<somewhere>
>
> then simply
> cp /bin/sed /mnt/<somewhere>/bin/
>
> then unmount it, re-gzip it and away you go!
>
> And what *I'd* like to know is why isn't sed on the
> initrd in the first plade if the scripts need it??
Well, it seems not all had the same problem, so I don't know!!??
--
regs
rupert
next prev parent reply other threads:[~2001-05-22 23:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 16:02 [linux-lvm] Converting my Root file system to LVM Rupert Heesom
2001-05-22 16:22 ` Rupert Heesom
2001-05-22 22:56 ` Steve Wray
2001-05-22 23:53 ` Rupert Heesom [this message]
2001-05-23 4:01 ` Steve Wray
2001-05-23 5:03 ` S. Michael Denton
2001-05-23 14:11 ` Rupert Heesom
2001-05-23 22:56 ` Andreas Dilger
2001-05-23 23:18 ` [linux-lvm] Is now: Resizing & LVM shutdown Rupert Heesom
2001-05-24 3:36 ` Austin Gonyou
2001-05-24 0:24 ` Rupert Heesom
2001-05-23 6:11 ` Glenn Shannon
2001-05-24 12:29 ` Ben Lutgens
2001-05-23 12:35 ` Glenn Shannon
2001-05-24 6:54 ` Andreas Dilger
2001-05-23 13:14 ` [linux-lvm] Converting my Root file system to LVM Rupert Heesom
2001-05-23 16:49 ` Andreas Dilger
2001-05-23 15:02 ` [linux-lvm] Converting my Root file system to LVM [last question] Rupert Heesom
2001-05-23 22:24 ` [linux-lvm] Converting my Root file system to LVM [lastquestion] Steve Wray
2001-05-24 6:41 ` Andreas Dilger
2001-05-24 10:52 ` Rupert Heesom
2001-05-24 22:07 ` Steve Wray
2001-05-24 14:22 ` AJ Lewis
2001-05-24 19:48 ` Luca Berra
2001-05-22 23:25 ` [linux-lvm] Converting my Root file system to LVM Andreas Dilger
2001-05-23 13:14 ` Michael Tokarev
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=990575643.1151.0.camel@localhost \
--to=raheesom@navpoint.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.