From owner-freebsd-stable@freebsd.org Tue Jun 21 03:35:27 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D498FAC5AB2 for ; Tue, 21 Jun 2016 03:35:27 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 528ED2783 for ; Tue, 21 Jun 2016 03:35:27 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from [IPv6:2a02:2698:22:b7ae:e14f:7af5:133b:5e30] (dynamic-2a02-2698-22-0-0.perm.ertelecom.ru [IPv6:2a02:2698:22:b7ae:e14f:7af5:133b:5e30] (may be forged)) (authenticated bits=0) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPSA id u5L3ZN5F039912 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Tue, 21 Jun 2016 08:35:24 +0500 (YEKT) (envelope-from emz@norma.perm.ru) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=norma.perm.ru; s=key; t=1466480124; bh=4bqAZU7M3s4fzWnN2tLyOYMnKLQOM6VgenVPdgyyjFA=; h=To:From:Subject:Date; b=hKDm3XGd44GQFACzPt/AtlaYgK+QQjsd9D1wZpGwQSVdzqtDes/dlt8mXGR+nVSXx Q+WyjGwSeuf+DNsVxNV0zkMf+YWe8zomnS+VUJ/NJ0XuZhpkoVGe+dk1Tjm7LG2aP7 5Be9msb87wOzyzL6DXIrba7/n58wOjh3U69XIQ0I= To: freebsd-stable@FreeBSD.org From: "Eugene M. Zheganin" Subject: FreeBSD as iSCSI target and VMWare ESX Message-ID: <547bf99b-6425-2a99-b4e8-eaa7d88406ab@norma.perm.ru> Date: Tue, 21 Jun 2016 08:35:25 +0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2016 03:35:27 -0000 Hi. Guys, does someone have experience with multiple LUNs on a target in ctld ? Recently I was installing ESX on a bunch of diskless hosts, connected to FreeBSD ctld. I was organizing them inside one target, multiple LUNs. As soon as the _count_ of LUNS went over 9, the whole thing went crazy - ESX were unable to install, showing multiple errors and not showing more than 10 LUNs from FreeBSD (and they were 11), and even the last one created was unsuitable for installation. As soon as I placed these "extra" LUNs inside the separate targets and LUN 0, everything went back to normal. I understand completely this sounds like a bad dream. I checked the VMWare limitations (https://www.vmware.com/pdf/vsphere5/r55/vsphere-55-configuration-maximums.pdf) - seems like it's supporting 256 LUNs per server. I've also checked their "iSCSI Best Practices Guide" and nowhere is says "use one LUN from a target". It's not fair to suspect FreeBSD from the start, but this ML is a much more frendlier place (at least I feel it to be so) - so, does anyone have experience providing more than 9 LUNs from a target ? Because I don't - prior to this I was providing one LUN from each target, and it seems that I will continue to do so. Thanks. Eugene.