From owner-freebsd-scsi@FreeBSD.ORG Sun Feb 3 17:35:31 2013 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 57A1C338 for ; Sun, 3 Feb 2013 17:35:31 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB2925B for ; Sun, 3 Feb 2013 17:35:29 +0000 (UTC) Received: from [192.168.135.7] (quaver.net [76.14.49.207]) (authenticated bits=0) by ns1.feral.com (8.14.5/8.14.4) with ESMTP id r13HZI1A032716 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 3 Feb 2013 09:35:23 -0800 (PST) (envelope-from mjacob@freebsd.org) Message-ID: <510E9FD1.5070907@freebsd.org> Date: Sun, 03 Feb 2013 09:35:13 -0800 From: Matthew Jacob Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, j@uriah.heep.sax.de Subject: Re: Multiple FreeBSD SCSI Hosts References: <510E987C.4090509@oxit.fi> In-Reply-To: <510E987C.4090509@oxit.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Sun, 03 Feb 2013 09:35:23 -0800 (PST) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mjacob@freebsd.org List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Feb 2013 17:35:31 -0000 On 2/3/2013 9:03 AM, Jukka A. Ukkonen wrote: > > a multiply attached SCSI device can be used as the trusted For SANs or iSCSI this can make some sense- but only if you really really trust the release mechanism (which I don't in any heterogeneous environment). The other question to raise is how do you sensibly represent the disks to the non-winner node and field failed attempts to operate on the shared disk? In other words, how do percolate RESERVATION CONFLICT errors up to the application level?