From owner-freebsd-current@FreeBSD.ORG Fri Oct 31 18:49:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA00D1065693 for ; Fri, 31 Oct 2008 18:49:01 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 5E4B68FC0C for ; Fri, 31 Oct 2008 18:49:00 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id m9VICUGv068913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 31 Oct 2008 13:12:31 -0500 (CDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id m9VICT3e068912; Fri, 31 Oct 2008 13:12:29 -0500 (CDT) (envelope-from dan) Date: Fri, 31 Oct 2008 13:12:29 -0500 From: Dan Nelson To: Javier =?utf-8?Q?Mart=C3=ADn?= Rueda Message-ID: <20081031181229.GC47647@dan.emsphone.com> References: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com> <490B3FB2.2040106@diatel.upm.es> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <490B3FB2.2040106@diatel.upm.es> X-OS: FreeBSD 7.1-PRERELEASE User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-current@freebsd.org, Daniel Jameson Subject: Re: ZFS attaching direct access drives as Scsibus#target#drive# X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Oct 2008 18:49:01 -0000 In the last episode (Oct 31), Javier Martín Rueda said: > Daniel Jameson escribió: > > I'm in the process of building several zfs pools for a > > backup-server, the machine has 2 24 port sata 3 controllers and 48 > > 1TB drives for storage. I've done a little testing and found that > > building a pool by using the da# device names can be inconsistent. > > For example if a device is lost from the first controller and the > > box is re-booted all the da#s shuffle up, which creates problems > > with adjacent pools, and the potential for catastrophic failure. In > > the Sun documentation zpool allows a pool to be built by using > > S#T#D# (Scsibus Target Drive) syntax, when I attempt it in FBSD It > > returns:" cannot use '/dev/c0t0d0': must be a GEOM provider" does > > anyone know a way to statically map a scsibus/target/drive to a > > specific da# or a fix to allow specific drives by target numbers to > > be added to a zpool? > > You can edit /boot/device.hints to associate specific SCSI ids to > specific da entries. Try something like this: Another method is to use glabel to label your devices, then build your zpools on the labeled devices: (root@dan) /root># glabel status Name Status Components label/da0_zfs_local N/A da0s1d label/da1_zfs_local N/A da1s1d (root@dan) /root># zpool status pool: local state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM local ONLINE 0 0 0 mirror ONLINE 0 0 0 label/da1_zfs_local ONLINE 0 0 0 label/da0_zfs_local ONLINE 0 0 0 errors: No known data errors -- Dan Nelson dnelson@allantgroup.com