From: Peter T. Breuer <ptb@lab.it.uc3m.es>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Re: raid 1 on a single disk
Date: Sat, 13 Nov 2004 13:59:19 +0100 [thread overview]
Message-ID: <72dh62-4om.ln1@news.it.uc3m.es> (raw)
In-Reply-To: 89af10f90411130241e20e2c2@mail.gmail.com
ashwin chaugule <ashwin.chaugule@gmail.com> wrote:
(please do not top post - fixing. Please take note!)
> > > Is this correct if I want data to be mirrored across all 4 partitions
> > > , using RAID 1 on a single disk ?
> >
> > So, you are talking about a mirror with 4 components, all of them
> > partitions on the same disk?
> >
> > Well, that's silly, but nothing stops you doing it. Just maek a raidtab
> > for the mirror and name the partitions as raid-disk components there.
> > The RAID howto or faq should tell you all you need to know, as should
> > the mananpage for the conf file or mdadm, or whatever ...
> ok so, i also do know, its performance is going to suck !
No, it'll be fine - merely a couple or more times slower at writing
large streams. In ordinary use you may sometimes see more latency, but
provided you aren't streaming or running synchronous writes, you
shouldn't notice. What's silly is that there's no point in doing it -
you get no protection against the disk disappearing, because all the
mirror components are on the same disk.
It's like making 3 sets of spare housekeys, and then putting them all
in the same keyholder as the original set, and walking around like that.
Silly, no?
> but i was under the impression that RAID 1 works on more that one disks only.
I don't understand you. While a mirror with only one component is
trivial, it is a mirror.
> so you mean to say that, the linux RAID / md tools support raid 1 on
> multiple partitiions of the same disk ?
Nobody cares where the mirror components are physically sited except
you. Why should any tool care? Its job is to do what you say. I don't
understand why you should think that the tool would even know (well,
there is a chance that it could look and check, but I don't recall any
significant code in the driver dedicated to optimizations based on that).
Peter
next prev parent reply other threads:[~2004-11-13 13:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 10:17 [linux-lvm] raid 1 on a single disk ashwin chaugule
2004-11-13 10:33 ` [linux-lvm] " Peter T. Breuer
2004-11-13 10:41 ` ashwin chaugule
2004-11-13 11:03 ` Piete Brooks
2004-11-13 12:59 ` Peter T. Breuer [this message]
2004-11-13 13:38 ` Piete Brooks
2004-11-13 15:04 ` Peter T. Breuer
2004-11-13 13:38 ` ashwin chaugule
2004-11-13 21:13 ` Graham Wood
2004-11-13 22:00 ` Greg Freemyer
2004-11-14 0:41 ` Måns Rullgård
2004-11-14 5:44 ` ashwin chaugule
2004-11-14 11:28 ` Peter T. Breuer
2004-11-14 17:41 ` ashwin chaugule
2004-11-14 18:04 ` Peter T. Breuer
2004-11-14 19:02 ` ashwin chaugule
2004-11-14 21:01 ` Peter T. Breuer
2004-11-15 6:09 ` ashwin chaugule
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=72dh62-4om.ln1@news.it.uc3m.es \
--to=ptb@lab.it.uc3m.es \
--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