From owner-freebsd-scsi@FreeBSD.ORG Tue Jan 20 13:18:01 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FCA816A4CE for ; Tue, 20 Jan 2004 13:18:01 -0800 (PST) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C8F043D54 for ; Tue, 20 Jan 2004 13:18:00 -0800 (PST) (envelope-from julian@vicor.com) Received: from vicor.com (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 79B867A3D4 for ; Tue, 20 Jan 2004 13:18:00 -0800 (PST) Message-ID: <400D9B08.70005@vicor.com> Date: Tue, 20 Jan 2004 13:18:00 -0800 From: Julian Elischer Organization: VICOR User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: SCSI@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: CAM//SCSI disk timeouts X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jan 2004 21:18:01 -0000 If we are talkign to a raid array and it discovers that it has to do some maintanance (e.g. declare a physical disk bad or recreate some data on the fly) it is possible that transactions to the raid that are outstanding may tak a lot longer than usual. In particular, we've seen the case where a log entry in teh Raid controller's log that indicates that a drive has been declared bad, is often accompanied in FreeBSD with a set of CAM /scsi-disk timeouts and things degrade from there... Where can I find the timeouts in force fo rscsi disks and teh retry policies? I need to compare the theoretical behaviour of FreeBSD CAM with the theoretical timeouts needed for the raid array, given a disk failure..