From: Hans Reiser <reiser@namesys.com>
To: "Rudy L. Zijlstra" <rudy@edsons.demon.nl>
Cc: the filesystem <reiserfs-list@namesys.com>
Subject: Re: OT: Advice on SATA sought
Date: Mon, 29 Mar 2004 07:49:27 -0800 [thread overview]
Message-ID: <40684587.2010001@namesys.com> (raw)
In-Reply-To: <406605A4.7020903@edsons.demon.nl>
Rudy L. Zijlstra wrote:
> Greetings,
>
>
> I am considering buying some 250G SATA drives (3 in a RAID5 config)
> for multimedia backend storage.
> disks will likely be WD SATA WD2500JD unless somebody points out good
> reasons not to. Can get those for about 200 Euro excluding VAT each.
> This is going to be used to store interactively accessed MPEG2 video
> files. They will be stored from at least 2 (on short notice 3)
> sources, and simultaously read from 2 or 3 locations. In other words:
> storage backend for a MythTV setup with 2 or 3 backends, and multiple
> frontends using a combination of PVR-250 and PVR-350s. 350 for
> frontend connected to a TV, several frontends using X for output.
>
> The controller i am considering is the Promise SATA TX4.
> kernel: 2.6.4 or later from kernel.org on a recent slackware-current
> distro.
>
> Any experience, either with this controller, with SATA, with other
> controllers, please share so I can make a better decision. I've
> currently no real experience with SATA.
>
> Filesystem choice has been made: Reiserfs3. This is going to be a
> production machine, I will not yet test Reiserfs4 on that. Too risky
> considering "comments" i would get on failure...
>
> Regards,
>
> Rudy
>
>
>
xfs might be better for this than v3, to be honest. delayed allocation
matters for this workload.
--
Hans
next prev parent reply other threads:[~2004-03-29 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-27 22:52 OT: Advice on SATA sought Rudy L. Zijlstra
2004-03-29 15:49 ` Hans Reiser [this message]
2004-03-29 19:08 ` Matt Stegman
2004-03-29 20:25 ` Boyd Waters
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=40684587.2010001@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=rudy@edsons.demon.nl \
/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.