From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM newbie question.
Date: Tue Jul 23 09:09:02 2002 [thread overview]
Message-ID: <6290000.1027433167@duke> (raw)
In-Reply-To: <Pine.OSF.4.33.0207231638100.7125-100000@newt.phys.unsw.edu.au>
Have you read the FAQ?
> When I do a pvcreate on say /dev/sda1 does that destroy all the existing
> data on that partition?
Why would you run pvcreate on a non-empty partition? The
only thing you'd do after that would be creating LV's
which will overwrite any data on the partition.
> Which is better for pvcreate to be used on a whole disk (pvcreate
> /dev/sda) and destroy all the underlying data or for me to merge all my
> existing paritions over to PV to combine in a volume group? Is there any
> advantage over either?
Depends on how many disks you have. If have only a
single disk then you're better off w/ a root partition
and some swap outside LVM in case you have to recover
from a situation in which LVM has problems. At that
point you can parition a disk with, say, 120MB, 64MB,
2GB, <the rest> w/ types 83, 82, 83, and 8e. This
allows you to install the system w/ the 3rd partition
as /usr if your distribution doesn't support LVM out of
the box or use it for scratch space. If /usr is a mount
point then the root can comfortably be 128MB.
> I've read the LVM how-to and am stilll alittle confused having never done
> it in practice. One part of the how-to said converting a root system to
> LVM is not recommended. SHould your OS directories /var / /boot
> etc all not be included in the LVM? That was the main idea behind me
> implementing LVM so that specific partitions (say var) could be resized at
> a later date if needed.
If /usr is a mount point then having /boot as a separate
mount is extraneous. If the machine isn't a 7x24 server
you can probably get by with /var on LVM; for a hard-core
system having /var on a partition is useful in case LVM
fries. Make /var 320MB and use a separate /scratch partition
for building new code, &c, and the only thing you'll need
on /var is spooling and logs, which will be unlikely to
outrun a 320MB partition.
> Will I have any trouble restoring my system (which I backed up using dd
> with a BS of 1024k) Do I have to make the LV the same size as my original
> partition were for this to work?
You cannot perform backups with dirty dump (dd). Use dump or
cpio to back the system up before touching LVM. At the
simplest:
find / |
egrep -v '/(proc|tmp|cache)/' |
cpio -ov -Hcrc --io-size=$((80*1024*1024)) --file=$TAPE 2>&1 |
tee /var/log/backup.log;
would give a full system backup to the tape device.
For a full backup using cpio -it --io-size=$((1024*1024*80)) --file=$TAPE
to check the archive is highly recommended.
Pick up a copy of Frisch, Essential System Administration, (3rd ed,
O'Reilly Press, 2002) for recommendations on this; Nemeth, et al,
Unix System Administrator's Handook (3rd ed) is also an excellent
read.
--
Steven Lembark 2930 W. Palmer
Workhorse Computing Chicago, IL 60647
+1 800 762 1582
next prev parent reply other threads:[~2002-07-23 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 1:49 [linux-lvm] LVM newbie question Melinda Taylor
2002-07-23 9:09 ` lembark [this message]
2002-07-23 9:49 ` bscott
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=6290000.1027433167@duke \
--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.