From owner-freebsd-scsi@FreeBSD.ORG Thu Jan 20 03:34:55 2011 Return-Path: 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 E86FD106564A; Thu, 20 Jan 2011 03:34:55 +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 A445F8FC17; Thu, 20 Jan 2011 03:34:55 +0000 (UTC) Received: from aannecy-552-1-220-142.w109-208.abo.wanadoo.fr ([109.208.220.142] helo=keklolwtf.home) by smtp.domeneshop.no with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1PflIT-0007NB-JV; Thu, 20 Jan 2011 04:34:53 +0100 Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Joachim Tingvold In-Reply-To: Date: Thu, 20 Jan 2011 04:34:50 +0100 Content-Transfer-Encoding: 7bit Message-Id: <07392102-4584-4690-9188-5202728CC7CA@tingvold.com> References: <4D2DAA45.30602@FreeBSD.org> <41C64262-4300-4187-B5FD-04A5EFB7F87C@tingvold.com> <20110113203750.GA39494@nargothrond.kdm.org> <20110114001758.GA12793@nargothrond.kdm.org> To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.1076) Cc: Alexander Motin , "Kenneth D. Merry" Subject: Re: mps0-troubles X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2011 03:34:56 -0000 On Fri, Jan 14, 2011, at 01:38:27AM GMT+01:00, Joachim Tingvold wrote: >> I don't think so. If anything, I think that this is likely >> triggered by >> a large number of outstanding commands, or perhaps a leak >> somewhere. If >> it's the former, hopefully this will fix it. If it's the latter, >> you'll >> eventually run into the problem again. > > Okay. I've changed the value. I'll keep you posted. Some more errors; . Same as earlier, but without the "out of chain"-messages (probably just because I increased the number, so that this specific error- message isn't printed?). This happened without direct user-interaction (it's a cron-job that copies files from 'zroot' to 'storage', and deletes some stuff on 'zroot' afterwards). However, it seems as if I can access the files/ folders on 'storage' without the terminal freezing (based on the log- messages, I was able to pinpoint the last 2-3 copied folders, and those I could list/copy files from without the terminal freezing). I'm not sure why, though. Maybe because the error/crash occurred when no files where being copied/moved? -- Joachim