From owner-freebsd-scsi@FreeBSD.ORG Thu May 8 13:45:39 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 4EA4BBFE for ; Thu, 8 May 2014 13:45:39 +0000 (UTC) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id EC6D5135 for ; Thu, 8 May 2014 13:45:38 +0000 (UTC) Received: from Mail-PC.tdx.co.uk (storm.tdx.co.uk [62.13.130.251]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id s48DjZWK064677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 May 2014 14:45:36 +0100 (BST) Date: Thu, 08 May 2014 14:45:35 +0100 From: Karl Pielorz To: freebsd-scsi@freebsd.org Subject: 'Wiring down' iSCSI devices / stop swapping dev nodes... Message-ID: <963D4F6D5D95769A2C8A07D1@Mail-PC.tdx.co.uk> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2014 13:45:39 -0000 Hi, I'm using the new iSCSI stack on FreeBSD 10. Seems to work fine so far - but I've noticed an issue (which is probably not related to new/old stack). I have a number of iSCSI targets setup - when they initially connect, they appear as '/dev/da[6/7/8/9/10/11/12/13]' However, if the remote node dies - when the iSCSI targets reconnect some of the drives transpose positions. I'm not specifically reconnecting them - just bringing the remote back up (when ctld / iscsid load up) - causes the local node to 'see' the drives have returned after a while (i.e. I don't run any iscsictl commands or anything). e.g. This time round drive previously connected to '/dev/da11' has now transposed with the drive that was connected to '/dev/da12' Is there any way I can prevent this? - i.e. by pre-alloctating / specifying '/dev/da' entries for devices or something? It's easy to see it happening on this test system as the drives are a mix of 750Gb and 2Tb - so when a 2Tb switches places with a 750Gb it's pretty obvious :) -Karl