From: carl.lowenstein@gmail.com (Carl Lowenstein)
Subject: [TUHS] 6th Edition RAID
Date: Wed, 1 Jul 2009 12:10:58 -0700 [thread overview]
Message-ID: <5904d5730907011210h5ebf8061y381e267fd313aad3@mail.gmail.com> (raw)
I thought I remembered something interesting about 6th Edition RK05
handlers, and went back to check RK(IV) in the manual. There it is,
Raid 0.
"Drive numbers (minor devices) of eight and larger are treated
specially. Drive 8+x is the x+1 way interleaving of devices rk0 to
rkx. Thus blocks on rk10 are distributed alternately among rk0, rk1,
and rk2." Goes on to enumerate precautions, like don't use the same
physical drive for both normal and interleaved operation.
I myself never tried this, because I didn't have enough confidence in
the error-free operation of a single RK05 drive, let alone two or
more. Note that this feature disappeared by the time of 7th Edition
RK(4).
carl
--
carl lowenstein marine physical lab u.c. san diego
clowenstein at ucsd.edu
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next reply other threads:[~2009-07-01 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 19:10 Carl Lowenstein [this message]
2009-07-02 8:53 ` Tim Bradshaw
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=5904d5730907011210h5ebf8061y381e267fd313aad3@mail.gmail.com \
--to=carl.lowenstein@gmail.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).