Date: Fri, 14 Apr 2006 11:02:17 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Paul Saab <ps@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD Crash without Errors, Warnings, or Panics Message-ID: <443F7329.8000804@dial.pipex.com> In-Reply-To: <443F1C21.4040109@freebsd.org> References: <443E95C1.4030404@digitalstratum.com> <443EE652.1020806@freebsd.org> <443F184C.4030306@digitalstratum.com> <443F1C21.4040109@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Saab wrote: > The amr driver was not MPSAFE in 5.4 (i think) so you would not have > run into these problems. You should be able to just take the driver > from RELENG_6 and use it on a released branch. If it doesn't compile, > let me know and I'll generate you a tarball or diff that will work. > We had major issues with amr at work until Scott Long and I (mostly > Scott) helped iron out the stability issues with amr. You should > either run RELENG_6 or take the driver from RELENG_6 and use that. > You'll get the added benefit of being able to use the Linux management > tools (megarc) to see the status of your raid. > Presumably this change will make it into 6.1 and is already in the betas/RCs? I'm confused by the megarc comment. There is a port of megarc in the ports which appears to work under 5.4 already, though I've only used it for simple reporting. I've seen references to Scott and your work on improving the driver which uses the same phrase "Linux management tools" but have no real idea what that refers to. Are there tools beyond megarc which now work? If so, any pointers much appreciated. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443F7329.8000804>