From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56007) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMAsd-0003oh-ME for qemu-devel@nongnu.org; Mon, 03 Aug 2015 04:13:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMAsV-0000em-BY for qemu-devel@nongnu.org; Mon, 03 Aug 2015 04:13:55 -0400 Received: from mail-wi0-x235.google.com ([2a00:1450:400c:c05::235]:35606) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMAsV-0000ef-4s for qemu-devel@nongnu.org; Mon, 03 Aug 2015 04:13:47 -0400 Received: by wibxm9 with SMTP id xm9so109700087wib.0 for ; Mon, 03 Aug 2015 01:13:45 -0700 (PDT) Sender: Paolo Bonzini References: <55BF0DFA.4000403@kamp.de> From: Paolo Bonzini Message-ID: <55BF22B9.8070101@redhat.com> Date: Mon, 3 Aug 2015 10:13:45 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Forbid to pass lun 0 to iscsi driver List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Andrey Korolyov , Peter Lieven Cc: "qemu-devel@nongnu.org" , ronnie sahlberg On 03/08/2015 09:47, Andrey Korolyov wrote: > I`ve mistyped lun for tgtd upon volume hotplug, which resulted in an > accidental crash, there is nothing but human factor. Until only LUN0 > may possess such unusual properties, I`d vote to explicitly work it > around instead of adding generic protection from volumes with > advertized zero block size. It's only tgtd, as far as I know, that makes LUN0 special. With lio (in-kernel target), for example, you can associate any kind of LUN to any LUN number. Paolo