From owner-freebsd-current@FreeBSD.ORG Tue Oct 14 21:32:42 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 E9EFF106569C for ; Tue, 14 Oct 2008 21:32:42 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 790498FC18 for ; Tue, 14 Oct 2008 21:32:42 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-066-030-118.pools.arcor-ip.net [88.66.30.118]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1KprVR0jBV-0002YT; Tue, 14 Oct 2008 23:32:41 +0200 Received: (qmail 4401 invoked from network); 14 Oct 2008 21:32:40 -0000 Received: from fbsd8.laiers.local (192.168.4.151) by mx.laiers.local with SMTP; 14 Oct 2008 21:32:40 -0000 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Tue, 14 Oct 2008 23:32:39 +0200 User-Agent: KMail/1.10.1 (FreeBSD/8.0-CURRENT; KDE/4.1.1; i386; ; ) References: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com> In-Reply-To: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810142332.39791.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1+ziXkkFUrYjqknsWH+ZlRGRpGGQGer9jH5RIn 1UI4setvgkABzKJGL0MzkCiS03t2jesscvNw8wS//D4a3+eghF hbawpfqdZ0xquo0EZzICA== Cc: 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: Tue, 14 Oct 2008 21:32:43 -0000 On Tuesday 14 October 2008 21:56:01 Daniel Jameson wrote: > 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? I though there was some magic to map devices by UID ... but I can't seem to find references to it right now. You can use glabel, however, and build the pool from the labeled devices instead. glabel disk0 /dev/da0 glabel disk1 /dev/da1 ... zpool create tank /dev/label/disk0 /dev/label/disk1 ... This will loose one sector at the end, but should otherwise have no negative effects. But you can juggle around devices as much as you like. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News