Date: Thu, 30 Jun 2005 15:06:27 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: "Douglas K. Rand" <rand@meridian-enviro.com> Cc: freebsd-stable@freebsd.org Subject: Re: What is considered "the best supported" RAID controller for 5.x? Message-ID: <20050630220626.GM727@funkthat.com> In-Reply-To: <8764vva5hk.fsf@delta.meridian-enviro.com> References: <20050617213910.M90456@ganymede.hub.org> <200506180943.j5I9hcOF019234@hugo10.ka.punkt.de> <20050629212908.GG727@funkthat.com> <8764vva5hk.fsf@delta.meridian-enviro.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Douglas K. Rand wrote this message on Thu, Jun 30, 2005 at 16:40 -0500:
> JM> Basicly a process will hang in either ffsfsn (fsync induces this
> JM> write) or getblk (a read), and as far as I can find out, the io
> JM> just never returns even though the underlying block device
> JM> continues to work fine..
>
> I know this is probably a stupid answer, but ... Have you upgraded
> the firmware on the card? We have a number of ICP cards and with the
> 2.39 firmware we can easily lockup the box with the behavior you
> explain with a simple buildworld. Upgrading the firmware to 2.44
> solves the problem completely for us.
Well, the problem is that it doesn't happen very often (only two
systems it happened to once), i.e. not reproducable, and to make matters
worse, we have 100+ systems in the field at client sites, so, w/o a
definate YES this fixes it, we can't really go around upgrading
firmware..
Plus, we have a lot of older cards, where the current firmware is
2.34 (though we are running on 2.32 for many of our cards)... so, we
can't use the really new firmware...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050630220626.GM727>