From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 11 22:07:30 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E34B6487 for ; Thu, 11 Sep 2014 22:07:30 +0000 (UTC) Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69B74C31 for ; Thu, 11 Sep 2014 22:07:30 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id z11so9823536lbi.26 for ; Thu, 11 Sep 2014 15:07:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=+m6Qj8/nWmRUtq4mcVSaydYpi7qbloCNLqV3HoqKgk0=; b=wacrc6/6HIfWTsjsq/jK752o0QqlDXGyWcQp5j3ozaCKKCV+zTqATR4UxY+cnW70GE Dy4kzjgP4rTXoRiMBpPN7AJizP+G+0IIxrnmWwjpZ0M8oDjxsr89MSwjzL69bisCO7Zv 9Mx1ItpX0bO6RnnveApxs2jkQK8pr7mSStjTMtP/lPxc7MvA46NSXBpHgual0cCMDbA6 97aPPJOEVbVXACE89O5Hy4fXf58F6h0JtQXnPeHBhzkqRt94WflrniTEA8Xq3JYKXRB3 LTT20hB3ryuAtlrqGeLeKKmhoPSghahTNlkLfI1WLDYhHkS5L3jaXqFCLo5yW1C+4SDY bndA== X-Received: by 10.112.62.200 with SMTP id a8mr4193541lbs.34.1410473248373; Thu, 11 Sep 2014 15:07:28 -0700 (PDT) Received: from pc5.home (abws48.neoplus.adsl.tpnet.pl. [83.8.242.48]) by mx.google.com with ESMTPSA id or5sm289740lbb.42.2014.09.11.15.07.27 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 11 Sep 2014 15:07:27 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 12 Sep 2014 00:07:24 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Chuck Tuffli Subject: Re: equivalent of Linux dev loss timeout? Message-ID: <20140911220724.GA3981@pc5.home> Mail-Followup-To: Chuck Tuffli , freebsd-scsi References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2014 22:07:31 -0000 On 0910T1243, Chuck Tuffli wrote: > Linux SCSI initiator drivers have the ability to send transport events > (e.g. link up/down) to a module that handles reporting and removing > devices from the system. By setting a "dev loss timeout", users can > specify how long a device can be missing before it is removed from the > system. > > As one example of how this is used, enthusiastic testers can run IO to > a device, yank out the cable between the initiator and the device for > less than dev loss timeout seconds, and then watch as the IO's resume > after the cable is reinserted. > > Does anything like this exist in CAM or would it be up to each SIM to > implement this behavior? Not strictly a timeout, but if you're looking for a way to "suspend" all IO operations to a disk device when it disappears, and reexecute them when it's connected back, in a transparent way, then gmountver might do the trick.