From: Daniel Pittman <daniel@rimspace.net>
To: linux-raid@vger.kernel.org
Subject: Re: Raid on USB2 ?
Date: Sat, 18 Feb 2006 12:11:28 +1100 [thread overview]
Message-ID: <87oe154gjj.fsf@rimspace.net> (raw)
In-Reply-To: 60F5F1E2B94AD4119F0B00B0D0215FFF01A6A25B@TEXTILES.BSC
Ken Walker <ken.walker@manchester.ac.uk> writes:
> Anybody tried a Raid1 or Raid5 on USB2.
>
> If so did it crawl or was it usable ?
Yes, I used this for two by two drive RAID-1 arrays.
It was usable, but not pleasantly. The machine became very I/O bound,
with human scale delays introduced into previously "instant" processes
such as opening an IMAP mailbox, scanning a directory listing, etc.
I wouldn't advise more than two or three drives per USB controller, and
would expect poor performance even then.
Daniel
next prev parent reply other threads:[~2006-02-18 1:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 10:54 Raid on USB2 ? Ken Walker
2006-02-17 11:03 ` Francois Barre
2006-02-17 14:30 ` Ewan Grantham
2006-02-18 1:11 ` Daniel Pittman [this message]
2006-02-18 9:48 ` PFC
2006-02-18 9:56 ` Gordon Henderson
-- strict thread matches above, loose matches on Subject: below --
2006-02-19 15:36 Alex Davis
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=87oe154gjj.fsf@rimspace.net \
--to=daniel@rimspace.net \
--cc=linux-raid@vger.kernel.org \
/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).