From: Anders Widman <andewid@tnonline.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM and fault tolerance
Date: Fri, 23 Mar 2001 00:59:26 +0100 [thread overview]
Message-ID: <3ABA91DE.29985185@tnonline.net> (raw)
In-Reply-To: Pine.LNX.4.30.0103211228450.8192-100000@flowers.house.larsshack.org
Lars Kellogg-Stedman wrote:
> > Is there any possibility to add fault tolerance to LVM. I would like
> > to span several disks (of different sizes) and have fault tolerance to
> > it. Also, most important, is to be able to extend it with additional
> > disks without loosing data.
>
> Disclaimer: I've only recently started working with LVM under Linux.
>
> That said, I think that the general solution to fault tolerance is to
> combine LVM with either (a) the software RAID (md) subsystem, or (b)
> hardware RAID devices.
>
Well, it will have to be software RAID (limited budget)
>
> For example, you can create a number of md devices, using RAID1 or RAID5
> for fault tolerance, and then run pvcreate on them and manage them with
> lvm.
>
> I'm doing this right now with a 4-disk RAID5 array (3 disks + 1 hot
> spare), and it seems to be working just fine.
>
So, how is this actually working then. Let say I have this disk
configuration:
2x 40gb
2x 60gb
2x 80gb
I want maximum amount of diskspace available for storage. High speed is not
needed at all as this is mainly for storage and streaming low bitrate media.
Still, I need to be able to add additional disks, maybe two extra 80gb
disks. Would it be possible to keep ecc/crc data on one disk only, or stripe
it over all disks. Mirroring is to expensive in this sence too.
The problem with RAID-5 is that all disks need to be of the same size and
that it is not expandable (or is it?).
//Anders
>
> -- Lars
>
> --
> Lars Kellogg-Stedman <lars@larsshack.org>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-03-22 23:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 20:13 [linux-lvm] vgscan won't recognize my VG David Vidal Rodriguez
2001-03-19 20:37 ` Andreas Dilger
2001-03-20 18:52 ` David Vidal Rodriguez
2001-03-20 19:17 ` AJ Lewis
2001-03-20 19:25 ` Andreas Dilger
2001-03-20 19:35 ` David Vidal Rodriguez
2001-03-20 20:00 ` David Vidal Rodriguez
2001-03-20 20:21 ` Andreas Dilger
2001-03-20 20:36 ` David Vidal Rodriguez
2001-03-21 0:29 ` Kirth
2001-03-21 18:30 ` David Vidal Rodriguez
2001-03-21 19:17 ` Andreas Dilger
2001-03-23 14:55 ` David Vidal Rodriguez
2001-03-23 22:36 ` Andreas Dilger
2001-03-20 20:57 ` [linux-lvm] LVM and fault tolerance Anders Widman
2001-03-21 17:33 ` Lars Kellogg-Stedman
2001-03-22 23:59 ` Anders Widman [this message]
[not found] ` <0103262137020G.01456@lyta>
2001-03-27 21:48 ` Anders Widman
2001-03-27 21:56 ` Ragnar Kjørstad
2001-03-27 22:29 ` Anders Widman
2001-03-27 22:45 ` Ragnar Kjørstad
2001-03-28 6:43 ` Russell Coker
2001-03-31 17:17 ` Anders Widman
2001-03-20 20:23 ` [linux-lvm] vgscan won't recognize my VG José Luis Domingo López
2001-03-20 19:31 ` AJ Lewis
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=3ABA91DE.29985185@tnonline.net \
--to=andewid@tnonline.net \
--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.