From owner-freebsd-current@FreeBSD.ORG Fri Jul 14 10:49:00 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9B8616A4E0 for ; Fri, 14 Jul 2006 10:49:00 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 01DF443D46 for ; Fri, 14 Jul 2006 10:48:59 +0000 (GMT) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.68.98) by 209.67.61.254 with SMTP; 14 Jul 2006 10:48:58 -0000 Date: Fri, 14 Jul 2006 13:48:30 +0300 From: Nikolay Pavlov To: Doug Ambrisko Message-ID: <20060714104830.GA13480@zone3000.net> References: <44B667C0.9010501@samsco.org> <200607131951.k6DJpKrZ021164@ambrisko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200607131951.k6DJpKrZ021164@ambrisko.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RELEASE Cc: John Baldwin , Joao Barros , current@freebsd.org Subject: Re: [PATCH] amr(4) testers needed... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 10:49:00 -0000 On Thursday, 13 July 2006 at 12:51:20 -0700, Doug Ambrisko wrote: > Scott Long writes: > | Joao Barros wrote: > | > On 7/11/06, John Baldwin wrote: > | > > | >> I have a patch for amr(4) that is a forward-port of a Scott Long patch > | >> for 4.x > | >> that fixes some severe data corruption with amr(4) + PAE on 4.x with > > | >> 4GB of > | >> RAM. I need the patch tested on current though so I can get it into > | >> HEAD and > | >> eventually into 4.x. The patch for head is at > | >> http://www.freebsd.org/~jhb/patches/amr_head.patch It shouldn't break > | >> anything and should basically be a nop. I think the patch will apply > | >> to 6.x > | >> (and possibly 5.x) as well. Thanks! > | >> > | > > | > I can test it on i386 without PAE. Is that test enough? > | > | Note that this problem is only present when you're using a management > | app at the same time as heavy disk activity is going on. If you're > | not using a management app (and few people are, the lack of apps is why > | I didn't catch this in the first place), then you're completely safe. > | John's email might be taken as a little alarmist in this respect. > > Hmm, I wonder why we don't see it or maybe we are :-( We don't usually > hit the disk hard but have a management app. running. I've seen > some strangeness. I am using this utility every hour in cron, now i have 4 processes in D state 24429 ?? D 0:00.01 /usr/local/sbin/megarc -ldInfo -LAll -a0 35394 ?? D 0:00.02 /usr/local/sbin/megarc -ldInfo -LAll -a0 37976 ?? D 0:00.02 /usr/local/sbin/megarc -ldInfo -LAll -a0 40526 ?? D 0:00.02 /usr/local/sbin/megarc -ldInfo -LAll -a0 I understand Scott position, but worried that megarc not killing by SIGKILL signal, it's not normal. I want to try preceding version of amr driver. Also i have 5.5 box as load balance pair for this one and never see such hangs on it. > > Doug A. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- ========================================================================= = Best regards, Nikolay Pavlov. <<<------------------------------------ = =========================================================================