Date: Fri, 04 Jun 2004 22:01:43 -0700 From: Bohdan Tashchuk <tashchuk@easystreet.com> To: freebsd-stable@freebsd.org Subject: Re: Dell PowerEdge 1600SC Server Message-ID: <40C153B7.9010606@easystreet.com> In-Reply-To: <3268737B-B4BD-11D8-99A8-000A9578CFCC@khera.org> References: <009201c444dc$4c2da450$2eca82ac@micasa.com> <200405281156.18711.scampbel@gvpl.ca> <40BD9D6B.7070207@parc.com> <3268737B-B4BD-11D8-99A8-000A9578CFCC@khera.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Vivek Khera wrote: >> You might want to reconsider the PERC controllers offered with that >> hardware. They (PERC3/SC and PERC4/SC) use the amr (megaraid) driver, >> and we've had serious stability problems under FreeBSD 4.9 and 5.2.1 >> with that controller > > > I'll counter this remark with a "works great here". I have a rack full > of Dell boxes with various Dell PERC controllers running FreeBSD 4.8 and > up. Some are amr devices, and some are aac devices. All work > flawlessly under quite substantial loads. On a Dell 600SC box with SCSI RAID, purchased in May 2003, Dell was quite anxious to make sure I received new firmware plus new Linux drivers. So you may check with them for firmware, though obviously the drivers won't do you any good. Which brings up an unfortunate situation when running unsupported software. When Dell updates the Linux driver to fix file corruption problmes, how do the changes make it into the FreeBSD driver? Usually the answer is, "they don't". Also, unfortunately I don't have easy access to the box, but I think it's running something very similar to PERC3. (PowerEdge RAID controller).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40C153B7.9010606>