From owner-freebsd-questions@FreeBSD.ORG  Fri Jun 26 17:09:49 2009
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4666E1065670
	for <freebsd-questions@freebsd.org>;
	Fri, 26 Jun 2009 17:09:49 +0000 (UTC)
	(envelope-from brentb@beanfield.com)
Received: from smtp0.beanfield.net (smtp0.beanfield.net [66.207.192.7])
	by mx1.freebsd.org (Postfix) with ESMTP id EED8D8FC13
	for <freebsd-questions@freebsd.org>;
	Fri, 26 Jun 2009 17:09:48 +0000 (UTC)
	(envelope-from brentb@beanfield.com)
Received: from brent.local ([66.207.193.249])
	by smtp0.beanfield.net (8.13.4/8.12.11) with ESMTP id n5QH7hN1070221
	for <freebsd-questions@freebsd.org>;
	Fri, 26 Jun 2009 13:07:43 -0400 (EDT)
	(envelope-from brentb@beanfield.com)
Message-ID: <4A4500D7.5090104@beanfield.com>
Date: Fri, 26 Jun 2009 13:09:43 -0400
From: Brent Bloxam <brentb@beanfield.com>
Organization: Beanfield Technologies
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Device naming on scbus using isp
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Jun 2009 17:09:49 -0000

I'm wondering about how device names are assigned on scbus, specifically 
when using the isp driver. It seems to me that there's potential when an 
HBA has access to multiple LUNs that on boot the scbus will have entries 
in /dev scrambled compared to the previous run (thus messing up mounts). 
My experience so far has been that da0 will be assigned to the first 
target scanned, da1 to the second, etc. Is this generally something 
countered with device.hints? If a LUN were to go away, but a device hint 
pointing to the target:unit remained, would that cause any issues on boot?

Thanks,
Brent