From: Brian Kress <kressb@moose.net>
To: A James Lewis <james@fsck.co.uk>
Cc: Chris Anderson <chris@alwan.com>,
h.milz@seneca.muc.de, "linux-lvm@msede.com" <linux-lvm@msede.com>
Subject: Re: [linux-lvm] Mirroring
Date: Sat, 12 Feb 2000 10:18:43 -0500 [thread overview]
Message-ID: <38A579D3.90A93436@moose.net> (raw)
In-Reply-To: Pine.LNX.4.20.0002111805300.18008-100000@vortex1.vrtx.net
A James Lewis wrote:
>
> What you're asking is can LVM be used in conjunction with MD, and is this
> the correct solution or is LVM/MD going to merge or LVM duplicate MD's
> work??
Yes. LVM on MD works great. I have a 4 disk
RAID 5 that I run LVM on to chop up into more managable
chunks. 40GB for a single FS is a bit excessive. I
do this with the new raid 0.90. I've never tried
it with the kernel standard raid, but I think I've
seem success reports.
Applying the LVM patch and the raid0.90 patch
gets you some errors in ll_rw_block.c, but if you know
C, you can pretty much figure out how to patch it by
hand. If anyone wants to do this and needs help with
the patches, I'd be happy to help.
LVM on top of MD is great. I get redundancy
and managability.
Brian
next prev parent reply other threads:[~2000-02-12 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 15:58 [linux-lvm] Mirroring Chris Anderson
2000-02-11 16:25 ` Harald Milz
2000-02-11 17:19 ` Chris Anderson
2000-02-11 18:06 ` A James Lewis
2000-02-11 18:16 ` Chris Anderson
2000-02-14 16:39 ` Luca Berra
2000-02-11 19:50 ` Chris McKinley
2000-02-12 0:18 ` Heinz Mauelshagen
2000-02-15 17:19 ` Mats Wichmann
2000-02-15 18:27 ` Michael Marxmeier
2000-02-12 15:18 ` Brian Kress [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-18 8:05 [linux-lvm] mirroring Jonathan E Brassow
2006-05-18 10:56 ` Jens Wilke
2006-05-18 10:56 ` Jens Wilke
2006-05-31 23:15 ` Harik A'ttar
2006-05-31 23:19 ` Harik A'ttar
1999-11-22 21:07 Michael Marxmeier
1999-11-22 21:55 ` James Pattinson
1999-11-22 20:59 Brian C. Huffman
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=38A579D3.90A93436@moose.net \
--to=kressb@moose.net \
--cc=chris@alwan.com \
--cc=h.milz@seneca.muc.de \
--cc=james@fsck.co.uk \
--cc=linux-lvm@msede.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.