From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: "Shaw, Marco" <marco.shaw@nbtel.nb.ca>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] lvm'ing root fs
Date: Tue, 11 Apr 2000 06:31:17 -0300 [thread overview]
Message-ID: <38F2F0E4.CA631C60@ednet.ns.ca> (raw)
In-Reply-To: E3A1ACFEDE71D3118C000020352285A03882E5@nbsjexm2.nbtel.nb.ca
I've used rsync to move a whole / filesystem.
rsync -avr --exclude-from=FILE /mnt_root_vg/* /.
Put anything you want excluded in the "FILE" file.
"Shaw, Marco" wrote:
> I've created an init ramdisk (lvmcreate_initrd), and now I'm in the process
> of trying to copy my root fs to my new lvm_root. To reduce the disk I/O,
> I've gone down to single user mode to try to copy (cp -a *) all my files
> from root to lvm_root. Twice I get the same results:
>
> # cd /
> # cp -a * /mnt/root_vg
> cp: /mnt/root_vg/proc/kcore_elf: Invalid argument
> cp: proc/sys/net/ipv4/route/flush: Invalid argument
>
> This is all I see on my screen, then at some point, the copying stops, and
> my system will not respond to keyboard input, except it will respond to
> Alt-F1/4 to switch virtual terms, but still no keyboard input accepted.
>
> Should I tar/untar instead, or did I miss some fundamental step?
>
> Thanks,
> Marco
next prev parent reply other threads:[~2000-04-11 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 0:59 [linux-lvm] lvm'ing root fs Shaw, Marco
2000-04-11 2:45 ` Andreas Dilger
2000-04-11 3:43 ` Peter C. Norton
2000-04-11 4:21 ` Peter C. Norton
2000-04-11 4:51 ` Michael Loftis
2000-04-11 5:10 ` Peter C. Norton
2000-04-11 5:24 ` Torsten Landschoff
2000-04-11 6:14 ` Ulf Bartelt
2000-04-11 8:43 ` Re[2]: " Jens Bruckmann
2000-04-11 19:01 ` Luca Berra
2000-04-11 5:22 ` Torsten Landschoff
2000-04-11 9:31 ` Patrick Boutilier [this message]
2000-04-11 9:32 ` Patrick Boutilier
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=38F2F0E4.CA631C60@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--cc=linux-lvm@msede.com \
--cc=marco.shaw@nbtel.nb.ca \
/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).