From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 23 07:12:33 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 DC33C16A418; Fri, 23 Nov 2007 07:12:33 +0000 (UTC) (envelope-from lol@chistydom.ru) Received: from hermes.hw.ru (hermes.hw.ru [80.68.240.91]) by mx1.freebsd.org (Postfix) with ESMTP id EBD5A13C44B; Fri, 23 Nov 2007 07:12:32 +0000 (UTC) (envelope-from lol@chistydom.ru) Received: from [80.68.244.40] (account a_popov@rbc.ru [80.68.244.40] verified) by hermes.hw.ru (CommuniGate Pro SMTP 5.0.13) with ESMTPA id 202397293; Fri, 23 Nov 2007 10:12:10 +0300 Message-ID: <47467D3F.7020002@chistydom.ru> Date: Fri, 23 Nov 2007 10:11:59 +0300 From: Alexey Popov User-Agent: Thunderbird 2.0.0.6 (X11/20070924) MIME-Version: 1.0 To: Kris Kennaway 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> In-Reply-To: <474492B0.1010108@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 23 Nov 2007 12:49:09 +0000 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 07:12:34 -0000 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? With best regards, Alexey Popov