From owner-freebsd-scsi@FreeBSD.ORG  Tue Feb  8 01:35:40 2011
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id EBBD0106566B;
	Tue,  8 Feb 2011 01:35:40 +0000 (UTC)
	(envelope-from joachim@tingvold.com)
Received: from smtp.domeneshop.no (smtp.domeneshop.no [194.63.248.54])
	by mx1.freebsd.org (Postfix) with ESMTP id A5A498FC18;
	Tue,  8 Feb 2011 01:35:40 +0000 (UTC)
Received: from aannecy-552-1-139-161.w86-200.abo.wanadoo.fr ([86.200.147.161]
	helo=keklolwtf.home)
	by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.72) (envelope-from <joachim@tingvold.com>)
	id 1PmcUV-0004aa-3C; Tue, 08 Feb 2011 02:35:39 +0100
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
From: Joachim Tingvold <joachim@tingvold.com>
In-Reply-To: <20110204180011.GA38067@nargothrond.kdm.org>
Date: Tue, 8 Feb 2011 02:35:35 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <DE11FC96-06DB-479F-8673-B9ACE2805390@tingvold.com>
References: <20110113203750.GA39494@nargothrond.kdm.org>
	<B22C5568-24D0-4530-B90A-BA6A6CAF111C@tingvold.com>
	<20110114001758.GA12793@nargothrond.kdm.org>
	<D24332F3-56AF-484C-9592-1097BF684E37@tingvold.com>
	<07392102-4584-4690-9188-5202728CC7CA@tingvold.com>
	<20110120155746.GA22515@nargothrond.kdm.org>
	<BC40CE83-6116-49CD-8D37-5BC29893449D@tingvold.com>
	<070C12D5-A54F-4A48-A151-EBA16EF32A13@tingvold.com>
	<20110203221056.GA25389@nargothrond.kdm.org>
	<FFF5EF18-055C-4E0C-8F9B-03564217F80F@tingvold.com>
	<20110204180011.GA38067@nargothrond.kdm.org>
To: Kenneth D. Merry <ken@freebsd.org>
X-Mailer: Apple Mail (2.1076)
Cc: freebsd-scsi@freebsd.org, Alexander Motin <mav@freebsd.org>
Subject: Re: mps0-troubles
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 01:35:41 -0000

On Fri, Feb 04, 2011, at 19:00:11PM GMT+01:00, Kenneth D. Merry wrote:
> Perhaps it could depend on memory fragmentation somewhat.  Over time  
> you
> may see the low water mark go down a bit.
>
> The good news is that it doesn't look like we have a leak.

<http://home.komsys.org/~jocke/dmesg_mps0_freebsd-scsi_5.txt>

[jocke@filserver ~]$ sysctl hw.mps.0
hw.mps.0.debug_level: 0
hw.mps.0.allow_multiple_tm_cmds: 0
hw.mps.0.io_cmds_active: 1
hw.mps.0.io_cmds_highwater: 959
hw.mps.0.chain_free: 2048
hw.mps.0.chain_free_lowwater: 1721
hw.mps.0.chain_alloc_fail: 0

This time I did a recursive copy of a folder with no large files at  
all (it contained only small documents), from 'storage' to 'storage'.

However, it recovered, so the copy just continued where it left of --  
which is a change from previous crashes.

-- 
Joachim