From: "Dieter Stüken" <stueken@conterra.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Uuid for unknown device blows up VolGroup00
Date: Fri, 30 Jun 2006 12:41:15 +0200 [thread overview]
Message-ID: <44A4FFCB.7040309@conterra.de> (raw)
In-Reply-To: <20060630055107.87219.qmail@web31410.mail.mud.yahoo.com>
Teak Billard wrote:
> In my getting wise period I read that the problem with volume groups is
> that if one hard drive fails, the entire volume group is finished. That
> to me is extremely dangerous. Am I right to be concerned?
If one hard disk fails, all data on THAT disk has gone.
As long as you have several small LV which completely
fit on a single disk, they are not lost, if some other
disk fails. The advantage of using LVM instead of plain
partitions is, that the LVs have real names instead of
ugly names like "/dev/sdb3", they may be resized and they
may be moved easily between different disks, even while
in use!
If you use LVM to bundle several disks to get bigger LVs
which spread over several disks, you depend on the reliability
of each disk. But this is the price you have to pay for
the plus of flexibility. You may feel saver, to separate
both disk by using separate LVs for each. So if one disk
fails, you saved one half of your data. So is this only
half as worse to loose only one half of your data?
If you work with individual disks and partitions, the
risk of accidentally deleting or formatting the wrong
disk or partition is much higher than with LVM, where
your "partitions" have expressive names. Also the LVM
commands prevent you from accidentally performing
destructive actions.
If your data is important, you have to make backups anyway.
If you worry about your data, you should buy reliable disks
or use a raid5 setup.
Dieter
prev parent reply other threads:[~2006-06-30 10:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 19:01 [linux-lvm] Uuid for unknown device blows up VolGroup00 Teak Billard
2006-06-29 8:17 ` Dieter Stüken
2006-06-30 5:51 ` Teak Billard
2006-06-30 10:41 ` Dieter Stüken [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=44A4FFCB.7040309@conterra.de \
--to=stueken@conterra.de \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).