From: "Miguel González Castaños" <mgc@tid.es>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and transferring filesystem
Date: Thu Mar 6 06:24:02 2003 [thread overview]
Message-ID: <3E673D81.7962C1AE@tid.es> (raw)
In-Reply-To: BDEMIPDEGABMNEFIHCPDAEJBEJAA.bill+f.9sfuw6uo@tao-group.com
Hello,
Many thanks for your promptly answer.
It works perfectly. I didnt know very much about the rsync command, i thought that It was only used to synchronize
files between hosts.
I also would like to know which is the best approach now, should i delete the original directories? any change in
the LVMed partitions will not be reflected in the original ROOTed directory but If I delete them, I wont be able
to boot without LVM (in the case I would need it and my LVMed partitions got corrupted).
Many thanks in advance
Miguel
William Blunn ha escrito:
> > I am installing a redhat 7.3 linux box with X-Window.
> >
> > I have installed LVM splitting the system with the following scheme:
> >
> > /boot and / are installed each in different non-LVM partitions.
>
> Smart move.
>
> > LVM volumes:
> >
> > /usr , /var/ , /tmp
> >
> > I have noticed that when I mount the filesystem using the LVM volumes
> > my X-Windows server doesnt work, but when I deactivate the LVM volumes
> > using the original configuration stored in the original / partition
> > (which still have the original /var, /tmp, /usr partitions) then
> > X-Window works perfectly.
> >
> > Then I assume that I havent transferred the filesystem well.
> >
> > I use from / the following command from the LVM howtos:
> >
> > tar cplf - -C var .|tar xvlf - -C /mnt/var
> >
> > and the same thing for the rest of partitions.
> >
> > Any suggestion?
>
> Permissions on /tmp ?
>
> Should be 1777 (drwxrwxrwt).
>
> To copy filesystems, I use:
>
> rsync -avxSHW --delete /var/ /mnt/var
>
> This has the added benefit that you can copy most data over whilst the system is up and running.
>
> Then you can take it down to single user, do the rsync again, and only the changed data will need to be copied.
>
> This minimises the time the system is in single user (which is good if you are working on a server).
>
> Bill
> --
> William H. Blunn - <bill+s.9sfuw6uo@tao-group.com> - Developer Support
> Tao
> 62/63 Suttons Business Park, Earley, READING, RG6 1AZ, United Kingdom
> Tel: +44 118 901 2999 - Fax: +44 118 901 2963 - http://tao-group.com/
>
> The contents of this e-mail and any attachments are confidential and may
> be legally privileged. If you have received this e-mail and you are not
> a named addressee, please inform us as soon as possible on
> +44 118 901 2999 and then delete the e-mail from your system. If you are
> not a named addressee you must not copy, use, disclose, distribute,
> print or rely on this e-mail. Any views expressed in this e-mail or any
> attachments may not necessarily reflect those of Tao's management.
> Although we routinely screen for viruses, addressees should scan this
> e-mail and any attachments for viruses. Tao makes no representation or
> warranty as to the absence of viruses in this e-mail or any attachments.
> Please note that for the protection of our business, we may monitor and
> read e-mails sent to and from our server(s).
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2003-03-06 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 5:28 [linux-lvm] LVM and transferring filesystem Miguel González Castaños
2003-03-06 5:57 ` William Blunn
2003-03-06 6:24 ` Miguel González Castaños [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=3E673D81.7962C1AE@tid.es \
--to=mgc@tid.es \
--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