Date: Tue, 24 Mar 2009 20:11:27 +0100 From: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= <peter@pean.org> To: Charles Sprickman <spork@bway.net> Cc: stable@freebsd.org Subject: Re: LSI Logic raid status Message-ID: <0B69CE4E-CC04-445B-9E84-C8E359136CCF@pean.org> In-Reply-To: <754A2F8B-21E7-493A-BD31-EA5691082D1E@bway.net> References: <91FBB56E-9B1F-469D-A83E-03396AA850FC@pean.org> <61AAA3A1-B794-4CF5-8F16-F30DB42940D9@verweg.com> <F0FE0D3A-7190-4877-9946-6542071EF731@pean.org> <754A2F8B-21E7-493A-BD31-EA5691082D1E@bway.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 24, 2009, at 8:00 PM, Charles Sprickman wrote: > > > dev.mpt.0.nonoptimal_volumes: 0 > > Don't test whether the "nonoptimal_volumes" parameter works, it does - > but if you pull a drive, FreeBSD likes to panic both on the loss of =20= > a disk > and then again when the drive is reconnected and the rebuild =20 > completes. > This is apparently some problem in the CAM layer, not the mpt =20 > driver, but > it's something to be aware of. Scott Long has noted that this is =20 > being > worked on in 8.x. Yes, I tried to remove a drive today. Of course I need to see if it =20 works properly before using it "for real". It did, but just as you say it paniced =20 when I pulled the drive and when is was resynced. But it sound great if someone is =20 working on this problem! -- Peter Ankerst=E5l peter@pean.org http://www.pean.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0B69CE4E-CC04-445B-9E84-C8E359136CCF>