From owner-freebsd-current@FreeBSD.ORG Wed Oct 15 11:04:51 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 A7E101065693 for ; Wed, 15 Oct 2008 11:04:51 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 860438FC1D for ; Wed, 15 Oct 2008 11:04:51 +0000 (UTC) (envelope-from marius@nuenneri.ch) Received: by rv-out-0506.google.com with SMTP id b25so2396704rvf.43 for ; Wed, 15 Oct 2008 04:04:51 -0700 (PDT) Received: by 10.115.73.20 with SMTP id a20mr628691wal.32.1224066747133; Wed, 15 Oct 2008 03:32:27 -0700 (PDT) Received: by 10.115.89.3 with HTTP; Wed, 15 Oct 2008 03:32:27 -0700 (PDT) Message-ID: Date: Wed, 15 Oct 2008 12:32:27 +0200 From: "=?ISO-8859-1?Q?Marius_N=FCnnerich?=" To: "Zaphod Beeblebrox" In-Reply-To: <5f67a8c40810142200o6074cd42hec0ff6f2b87d3648@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <0A8710FF880BBB4687AEC66F9DCF7D0C26B462@SERVER1.emerytelcom.com> <5f67a8c40810142200o6074cd42hec0ff6f2b87d3648@mail.gmail.com> 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: Wed, 15 Oct 2008 11:04:51 -0000 On Wed, Oct 15, 2008 at 7:00 AM, Zaphod Beeblebrox wrote: > On Tue, Oct 14, 2008 at 3:56 PM, 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? > > > Forgive me for asking (because it would surprise me if it didn't), but > doesn't ZFS' GEOM attach taste figure out what drives go where all by > itself? Isn't there sufficient information on a disk to allow ZFS to place > it into the correct pool? I think there is, take a look at this: http://blogs.sun.com/constantin/entry/csi_munich_how_to_save The Video is no longer at google video, but there is this working link at bottom: http://mediacast.sun.com/share/constantin/csi_muc_en.mp4 > > certainly glabel'ing the drives should work just fine if zfs doesn't, but > it's a hack of a solution. > > glabel can have some funny effects due to the geom taste order. If > something is part of a mirror (for instance) and the label tastes before the > mirror, I've seen items of the mirror come up with glabel instead of > attaching to the mirror. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >