From: Anders Widman <andewid@tnonline.net>
To: Hans Reiser <reiser@namesys.com>
Cc: bscott@ntisys.com, ReiserFS Mailing List <Reiserfs-List@namesys.com>
Subject: Re: Promise raid controller writes to disk, anybody know where?
Date: Wed, 16 Apr 2003 18:51:11 +0200 [thread overview]
Message-ID: <1389382.20030416185111@tnonline.net> (raw)
In-Reply-To: <3E9D88FB.6090109@namesys.com>
> bscott@ntisys.com wrote:
>>On Wed, 16 Apr 2003, at 8:24pm, reiser@namesys.com wrote:
>>
>>
>>>I just bought this motherboard with a promise raid controller builtin
>>>whose manual mentions that it writes information to disk (volume and
>>>config info I believe).
>>>
>>>
>>
>> Some RAID controllers write information to the disk, but never expose it
>>to the host OS. For example, say the RAID controller writes information to
>>the last block in the disk. The disk it then presents to the host OS will
>>be one block shorter. I don't know if your Promise "RAID controller" is
>>one of those.
>>
>> I put "RAID controller" in quotes because most Promise "RAID controllers"
>>are simply a more-or-less standard IDE interface, with RAID done in software
>>on the host (the software either comes from the BIOS, or the device driver).
>>You're likely better off using your OS's native software RAID in that event.
>>
>> Also, AFAIK, support for Promise RAID controllers under Linux (I assume
>>you're running Linux) is poor at best. You way want to avoid using it at
>>all.
>>
>>
>>
> Ok, I'll not use it then. I was thinking of mirroring, but I was
> assuming it was all done in hardware....
You can still use the controller, but I would do the mirroring
natively in Linux than depend on the Promise BIOS to do it.
--------
PGP public key: https://tnonline.net/secure/pgp_key.txt
next prev parent reply other threads:[~2003-04-16 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 16:24 Promise raid controller writes to disk, anybody know where? Hans Reiser
2003-04-16 16:28 ` Anders Widman
2003-04-16 16:42 ` bscott
2003-04-16 16:46 ` Hans Reiser
2003-04-16 16:51 ` Anders Widman [this message]
2003-04-16 16:54 ` Hans Reiser
2003-04-16 16:59 ` Anders Widman
2003-04-17 1:40 ` Hans Reiser
2003-04-16 18:04 ` bscott
2003-04-17 1:48 ` Hans Reiser
2003-04-16 18:05 ` bscott
2003-04-16 21:26 ` Soeren Sonnenburg
2003-04-16 21:37 ` Hendrik Visage
2003-04-16 21:38 ` Anders Widman
2003-04-17 6:01 ` Soeren Sonnenburg
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=1389382.20030416185111@tnonline.net \
--to=andewid@tnonline.net \
--cc=Reiserfs-List@namesys.com \
--cc=bscott@ntisys.com \
--cc=reiser@namesys.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 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.