From: Tomasz Chmielewski <mangoo@wpkg.org>
To: John Stoffel <john@stoffel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: checking md device parity (forced resync) - is it necessary?
Date: Wed, 06 Sep 2006 16:11:46 +0200 [thread overview]
Message-ID: <44FED722.2050508@wpkg.org> (raw)
In-Reply-To: <17662.54119.167225.879836@smtp.charter.net>
John Stoffel wrote:
> Tomasz> Lately I installed Debian on a Thecus n4100 machine. It's a
> Tomasz> 600 MHz ARM storage device, and has 4 x 400 GB drives.
>
> Interesting box... how quiet is it?
I can't tell you if it's quiet or not, it's in the server room right
now, and serves as a backup and iSCSI storage for Xen.
But as I still configured it and it was on my desk, it seemed a bit
louder than a normal PC.
After all, it has 4 drives (which you have to buy separately).
> I'm thinking of one of these for
> home use, but I'll probably go with an EPIA box so I can actually
> setup a NFS/CiFS/backup/http/mysql server...
Although it has two gigabit network cards, you can't fully use them -
the IXP3xx ARM CPU (600 MHz) allows you to only send about 25 MB/s of
packets (measured on a loopback interface, so iSCSI LAN speeds are a bit
lower).
> I've looked at the Irfant and the Buffalo Logic ones as well... all
> tempting. But backups are the killer. :]
There's also Thecus n5200, 800 MHz mobile Celeron, which you can supply
with 5 drives... :)
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2006-09-06 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 8:59 checking md device parity (forced resync) - is it necessary? Tomasz Chmielewski
2006-09-05 10:13 ` Neil Brown
2006-09-05 12:00 ` Tomasz Chmielewski
2006-09-05 16:59 ` Luca Berra
2006-09-06 7:19 ` Mario 'BitKoenig' Holbe
2006-09-06 8:12 ` Tomasz Chmielewski
2006-09-06 13:55 ` John Stoffel
2006-09-06 14:11 ` Tomasz Chmielewski [this message]
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=44FED722.2050508@wpkg.org \
--to=mangoo@wpkg.org \
--cc=john@stoffel.org \
--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).