From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 23 10:53:55 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71C3F16A418; Fri, 23 Nov 2007 10:53:55 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id A2A6513C468; Fri, 23 Nov 2007 10:53:53 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4746B148.6000209@FreeBSD.org> Date: Fri, 23 Nov 2007 11:54:00 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Alexey Popov References: <47137D36.1020305@chistydom.ru> <47149E6E.9000500@chistydom.ru> <4715035D.2090802@FreeBSD.org> <4715C297.1020905@chistydom.ru> <4715C5D7.7060806@FreeBSD.org> <471EE4D9.5080307@chistydom.ru> <4723BF87.20302@FreeBSD.org> <47344E47.9050908@chistydom.ru> <47349A17.3080806@FreeBSD.org> <47373B43.9060406@chistydom.ru> <4739557A.6090209@chistydom.ru> <4741EE9E.9050406@FreeBSD.org> <474492B0.1010108@FreeBSD.org> <47467D3F.7020002@chistydom.ru> In-Reply-To: <47467D3F.7020002@chistydom.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Panagiotis Christias , freebsd-stable@freebsd.org Subject: Re: amrd disk performance drop after running under high load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Nov 2007 10:53:55 -0000 Alexey Popov wrote: > Kris Kennaway wrote: > >>>>> what is your RAID controller configuration (read ahead/cache/write >>>>> policy)? I have seen weird/bogus numbers (~100% busy) reported by >>>>> systat -v when read ahead was enabled on LSI/amr controllers. >>>> I tried to run with disabled Read-ahead, but it didn't help. >>> I just ran into this myself, and apparently it can be caused by >>> "Patrol Reads" where the adapter periodically scans the disks to look >>> for media errors. You can turn this off using -stopPR with the >>> megarc gg port. >> Oops, -disPR is the correct command to disable, -stopPR just halts a >> PR event in progress. > Wow! Really disabling Patrol Reads solves the problem. Thank you! > > I have many amrd's and all of them appear to have Patrol Reads enabled > by default. But the problem happenes only on three of them. Is this a > hardware problem? I am not sure, maybe for some reason the patrol reads are not interfering with other disk I/O so much (e.g. the hardware prioritises them differently or something). Anyway, glad to hear it was resolved. Kris