<< Right, but the thing is, you don't even need RAID to have eight IDE devices. Many recent BX boards, for instance, implement an onboard ATA/66 controller to supplement the integrated ATA/33 channels, leaving you with room for eight high performance drives. And remember, not many file servers are going to use that many drives. Most small to moderate network file servers use, at most, two main drives and a backup. >>
So basically, you are recommending a server without fault tolerance, without the speed increase from the SCSI interface and without the higher quality you actually get from a high-end SCSI drive? I don't think any of that is acceptable. If i were to build such a server for any of my customers, they would certainly hang me the day one disk fails.
I have an example for you, i got involved in a new system setup in a local hardware store, they thought my server would be to expensive for them, then i calculated one day worth of lost data, and half a day worth of down-time, and guess what, my server wasn't very expensive anymore.
People who actually need servers (as opposed to peer-to-peer) actually need stability, therefore fault tolerance is a must, if a HDD crashes you cannot afford the downtime, and you cannot afford the lost information.
And getting back to the speed issue, this same hardware store actually got more out of adding another disk to their 5 disk RAID 5 than they did increasing the memory from 512MB to 1GB.
<< - Both SCSI and IDE file servers will be limitted by the 100Mbit (12.5M/s) network bandwidth. >>
Eh, that would be full duplex 1Gb ethernet for any server i build so the SCSI performance would not be limited by anything.
<< - Under light to moderate loads, neither SCSI nor IDE will suffer from multiple simulaneous data access, since this will be handled by the OS disk routines and cache memory. >>
Well, this simply is not true, first of all, i don't know what the 50 supposed users of this server would be doing in your example, but in mine, they would be working, perhaps accessing a Oracle database, maybe through a java interface (this is a real life example), for them the IDE solution would mean a considerable bottle neck, consuming way too much CPU time (fault tolerance is a MUST so this would be a RAID setup), and so again, this would not be acceptable.
<< Why do people buy overpriced Pentium III systems with Rambus memory? Why do they buy expensive rings with diamond instead of cubic zerconium, which has an identical index of refraction and therefore perfectly duplicates the only useful purpose of a diamond -- to sparkle and look pretty? Why do they buy name brand peanut butter when the generic store brand tastes the same? Simple. They assumed the extra cost translated into better product, and they never questioned that assumption. >>
And why on earth would anyone want to buy a Ferrari when the Lada is so cheap?? That angle goes both ways. And the only useful purpose of a diamond is to look pretty, oh, is that why they make diamond drills, because they look prettier??
This is getting silly, why can't you just accept that IDE is not always the best solution, and that for servers, SCSI is a far superior solution.
Patrick Palm
Am speaking for PC Resources