Date: Fri, 12 Sep 2014 00:07:24 +0200 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org> To: Chuck Tuffli <chuck@tuffli.net> Cc: freebsd-scsi <freebsd-scsi@freebsd.org> Subject: Re: equivalent of Linux dev loss timeout? Message-ID: <20140911220724.GA3981@pc5.home> In-Reply-To: <CAM0tzX0iHwmLt_QJ%2BePtppUvFhqK7_rsdWm5PXQhtPQuyQGY2Q@mail.gmail.com> References: <CAM0tzX0iHwmLt_QJ%2BePtppUvFhqK7_rsdWm5PXQhtPQuyQGY2Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140911220724.GA3981>