From: "Lars Täuber" <taeuber@bbaw.de>
To: David Lethe <david@santools.com>
Cc: Neil Brown <neilb@suse.de>, Anton Altaparmakov <aia21@cam.ac.uk>,
linux-raid@vger.kernel.org
Subject: Re: How to grow RAID1 mirror on top of LVM?
Date: Tue, 29 Apr 2008 09:55:45 +0200 [thread overview]
Message-ID: <20080429095545.305b2dfd.taeuber@bbaw.de> (raw)
In-Reply-To: <A20315AE59B5C34585629E258D76A97C2C79A0@34093-C3-EVS3.exchange.rackspace.com>
Hallo David!
"David Lethe" <david@santools.com> schrieb:
> Lars:
> Even if you *could* do this, then your design would still be an awful idea. You'd effectively have a random I/O filesystem. Any write on a RAID1 disk would generate writes on all of the other disks. Even with a small number of RAID1 targets and default journaling, I wouldn't be surprised if a single application write translated into at least a dozen physical disk writes.
>
> What if (when) both the RAID1 & RAID6 became corrupted? How would you proceed? How would you propose the md engine deal with this? What if you lose a disk on the RAID6 while expanding the LVM and have a bad sector on remaining disks, or fsck shows filesytem corruption while you are expanding a md volume.
>
> Maybe you are starting to get the point.
No, sorry. I really don't understand. But maybe because I didn't tell detailed enough what our systems looks like.
We have here two huge RAID6 systems, that are connected through a 10G Ethernet switch. They are equally in size.
On these RAID6 we create LVs euqally in size and want them to be parts of a RAID1:
RAID6 RAID6
monosan duosan
LV LV (multiple of)
\ / 10GE
RAID1
| 10GE
aoe
| 1GE
server (multiple of)
> What is preventing the md layer from doing what you want is that a heck of a lot of code would have to be written,
But could you tell me what in the current »design« prevents us to resize the LVs and the RAID1 on top?
When I understand it correctly the RAID information are written at the end of each accessible partition/LV.
What is different on an extended LV from a partition that is replaced with a bigger one?
[...]
Thanks
Lars
--
Informationstechnologie
Berlin-Brandenburgische Akademie der Wissenschaften
Jägerstrasse 22-23 10117 Berlin
Tel.: +49 30 20370-352 http://www.bbaw.de
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-04-29 7:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 11:21 How to grow RAID1 mirror on top of LVM? Anton Altaparmakov
2008-03-25 5:36 ` Neil Brown
2008-03-25 8:00 ` Anton Altaparmakov
2008-04-28 14:25 ` Lars Täuber
2008-04-28 15:09 ` David Lethe
2008-04-29 7:55 ` Lars Täuber [this message]
2008-04-29 13:21 ` David Lethe
2008-05-02 3:14 ` Neil Brown
2008-05-02 7:23 ` Lars Täuber
2008-05-02 15:06 ` Russ Hammer
2008-05-04 11:20 ` Neil Brown
2008-05-05 7:10 ` Lars Täuber
2008-05-06 12:34 ` Russ Hammer
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=20080429095545.305b2dfd.taeuber@bbaw.de \
--to=taeuber@bbaw.de \
--cc=aia21@cam.ac.uk \
--cc=david@santools.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.