From owner-freebsd-scsi@FreeBSD.ORG Mon Apr 12 17:03:24 2010 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 AD9781065674 for ; Mon, 12 Apr 2010 17:03:24 +0000 (UTC) (envelope-from westr@connection.ca) Received: from nc-tor-mail2.connection.ca (nc-tor-mail2.connection.ca [205.207.122.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8E31C8FC13 for ; Mon, 12 Apr 2010 17:03:24 +0000 (UTC) Received: from westr-main.tor.connection.ca (external.tor.connection.ca [216.234.38.18]) by nc-tor-mail2.connection.ca (Postfix) with ESMTP id CD1CD74E55A for ; Mon, 12 Apr 2010 13:03:23 -0400 (EDT) Date: Mon, 12 Apr 2010 13:03:23 -0400 From: Ross Organization: Network Connection X-Priority: 3 (Normal) Message-ID: <223938752.20100412130323@connection.ca> To: freebsd-scsi@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: isp driver - sysctl controls missing X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ross List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2010 17:03:24 -0000 It looks like in the isp(4) driver update that happened back when Freebsd v8.0 got updated, it looks like the user-modifiable sysctls got removed and timeouts are now hardcoded. The man page for isp state: -= SYSCTL OPTIONS dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visible. The default is 300 seconds (5 minutes). A seperate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. -= But checking over the driver code shows sysctl details are now removed and the hardcoded value for loop_down_limit is now 60 seconds and gone_device_time is 30 seconds. Anyone know if there's any reason for the sysctl is being pulled out, and the limits being so high? We use this in conjunction with geom multipath, so would prefer to fail over to another fc path asap when there's an issue. Cheers, Ross. --