Date: Sun, 01 Apr 2007 19:31:27 +0100 From: Richard Tector <richardtector@thekeelecentre.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: Matthew Jacob <lydianconcepts@gmail.com>, freebsd-stable@freebsd.org Subject: Re: Dell SAS5 Performance Issue Message-ID: <460FFA7F.1070902@thekeelecentre.com> In-Reply-To: <20070401164658.S36917@maildrop.int.zabbadoz.net> References: <460959E8.207@thekeelecentre.com> <7579f7fb0703271102q1a866897x2d63a86e72895125@mail.gmail.com> <46095CE5.5080600@thekeelecentre.com> <7579f7fb0703272018i68983d5cvb9fe84c79cebd473@mail.gmail.com> <460FCE61.7090006@thekeelecentre.com> <20070401164658.S36917@maildrop.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote: > On Sun, 1 Apr 2007, Richard Tector wrote: >> A perhaps unrealted issue: >> I've noticed a large number of messages being produced by the mpt >> driver after boot occuring approximately every 90 seconds. >> >> Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14 >> Apr 1 15:51:43 moses kernel: mpt0: Unhandled Event Notify Frame. >> Event 0x14 (ACK not required). >> Apr 1 15:53:19 moses kernel: mpt0: mpt_cam_event: 0x14 >> Apr 1 15:53:19 moses kernel: mpt0: Unhandled Event Notify Frame. >> Event 0x14 (ACK not required). >> >> Any thoughts anyone? Is there any way to find out what the events >> correspond to? > IMHO 0x14 is "resync complete". Dud you have a degraded RAID-1? > > Can you tell me what > > Index: mpt_cam.c > =================================================================== > RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/mpt/mpt_cam.c,v > retrieving revision 1.52 > diff -u -p -r1.52 mpt_cam.c > --- mpt_cam.c 11 Mar 2007 01:54:59 -0000 1.52 > +++ mpt_cam.c 1 Apr 2007 16:54:27 -0000 > @@ -2236,6 +2236,10 @@ mpt_cam_event(struct mpt_softc *mpt, req > CAMLOCK_2_MPTLOCK(mpt); > break; > } > + case MPI_EVENT_IR_RESYNC_UPDATE: > + uint8_t resync = (data0 >> 16) & 0xff; > + mpt_prt(mpt, "IR resync update %d completed.", resync); > + break; > case MPI_EVENT_EVENT_CHANGE: > case MPI_EVENT_INTEGRATED_RAID: > case MPI_EVENT_SAS_DEVICE_STATUS_CHANGE: > > gives you; especially how far it counts up? > Now you come to mention it, I believe it was indeed the array rebuilding. I'll try your patch and force a resync of the mirror tomorrow morning and report back with the output. Would be a useful feature to have. On a side note the array is now marked as Optimal in the BIOS so I assume the following messages, sent about 2 hours later, were various ways of saying "Complete"? Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x14 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x14 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x15 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x15 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Apr 1 18:31:43 moses kernel: mpt0: mpt_cam_event: 0x21 Apr 1 18:31:43 moses kernel: mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required). Thank you for your help, Richard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?460FFA7F.1070902>