From owner-freebsd-stable@freebsd.org  Mon Nov 16 20:57:41 2015
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8A8EA30828;
 Mon, 16 Nov 2015 20:57:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 703B91812;
 Mon, 16 Nov 2015 20:57:41 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1ZyQqE-000Obi-ST; Mon, 16 Nov 2015 23:57:34 +0300
Date: Mon, 16 Nov 2015 23:57:34 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Freddie Cash <fjwcash@gmail.com>
Cc: Kevin Oberman <rkoberman@gmail.com>, freebsd-scsi@freebsd.org,
 Royce Williams <royce@tycho.org>,
 freebsd-stable <freebsd-stable@freebsd.org>,
 Borja Marcos <borjam@sarenet.es>, Kai Gallasch <k@free.de>
Subject: Re: LSI SAS2008 mps driver preferred firmware version
Message-ID: <20151116205734.GM48728@zxy.spb.ru>
References: <5644FF09.9090200@free.de>
 <CA+E3k93QrUFA3BvhoswkVDXh2bR2aLYG6Z0TOrisVvNL=+MZVA@mail.gmail.com>
 <56472686.5030301@free.de> <20151114143104.GA41119@in-addr.com>
 <7710CBCC-E68F-4454-9E29-E50ED1C6B511@sarenet.es>
 <CAN6yY1sH0PnnF_AGwDsA75i_Z6ptOr4J0c_Gqrt+RFO6eZsW-Q@mail.gmail.com>
 <CAOjFWZ4Js65gQZc6rbT9SKg-jZozziTa=JGpJys6HyejdgWP+g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAOjFWZ4Js65gQZc6rbT9SKg-jZozziTa=JGpJys6HyejdgWP+g@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Nov 2015 20:57:41 -0000

On Mon, Nov 16, 2015 at 11:40:12AM -0800, Freddie Cash wrote:

> On Mon, Nov 16, 2015 at 11:36 AM, Kevin Oberman <rkoberman@gmail.com> wrote:
> 
> > On Mon, Nov 16, 2015 at 1:00 AM, Borja Marcos <borjam@sarenet.es> wrote:
> >
> > >
> > > On Nov 14, 2015, at 3:31 PM, Gary Palmer wrote:
> > >
> > > > You can do thinks in /boot/loader.conf to hard code bus and drive
> > > > assignments.
> > > >
> > > > e.g.
> > > >
> > > > hint.da.0.at="scbus0"
> > > > hint.da.0.target="19"
> > > > hint.da.0.unit="0"
> > > > hint.da.1.at="scbus0"
> > > > hint.da.1.target="18"
> > > > hint.da.1.unit="0"
> > >
> > > Beware, the target number assignment is not predictable. There's no
> > > guarantee especially if you replace
> > > a disk.
> > >
> > >
> > >
> > >
> > >
> > > Borja.
> > >
> >
> > As already mentioned, unless you are using zfs, use gpart to label you file
> > systems/disks. Then use the /dev/gpt/LABEL as the mount device in fstab.
> >
> 
> ​Even if you are using ZFS, labelling the drives with the location of the
> disk in the system (enclosure, column, row, whatever) makes things so much
> easier to work with when there are disk-related issues.
> 
> Just create a single partition that covers the whole disk, label it, and
> use the label to create the vdevs in the pool.​

Bad idea.
Re-placed disk in different bay don't relabel automaticly.
Other issuse where disk placed in bay some remotely hands in data
center -- I am relay don't know how disk distributed by bays.
Best way for identify disk -- uses enclouse services.

I have many sites with ZFS on whole disk and some sites with ZFS on
GPT partition. ZFS on GPT more heavy for administration.