From owner-freebsd-fs@FreeBSD.ORG  Mon Jun 10 03:26:24 2013
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 0AE27E53
 for <freebsd-fs@freebsd.org>; Mon, 10 Jun 2013 03:26:24 +0000 (UTC)
 (envelope-from wblock@wonkity.com)
Received: from wonkity.com (wonkity.com [67.158.26.137])
 by mx1.freebsd.org (Postfix) with ESMTP id C10E818D8
 for <freebsd-fs@freebsd.org>; Mon, 10 Jun 2013 03:26:23 +0000 (UTC)
Received: from wonkity.com (localhost [127.0.0.1])
 by wonkity.com (8.14.7/8.14.7) with ESMTP id r5A3QLJG075281;
 Sun, 9 Jun 2013 21:26:21 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Received: from localhost (wblock@localhost)
 by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r5A3QLjg075278;
 Sun, 9 Jun 2013 21:26:21 -0600 (MDT)
 (envelope-from wblock@wonkity.com)
Date: Sun, 9 Jun 2013 21:26:21 -0600 (MDT)
From: Warren Block <wblock@wonkity.com>
To: Jeremy Chadwick <jdc@koitsu.org>
Subject: Re: ZFS and Glabel
In-Reply-To: <20130610021950.GA50356@icarus.home.lan>
Message-ID: <alpine.BSF.2.00.1306092122550.75158@wonkity.com>
References: <CALOkxuzH81UFuVZifJNxyuo6+hu9mCPB1TC91dn5fkjVLFqTKw@mail.gmail.com>
 <CALOkxuxb0HBMXOwP6Z4JjvBk+btnriCeCdhcKfmP=FyNEaseTA@mail.gmail.com>
 <CALOkxuxT9Oko1jm40GzYZbcTNu4epNgh8BoVhc-cH2UKNNbSvw@mail.gmail.com>
 <20130609065430.GA28206@icarus.home.lan>
 <CALOkxuwVDYmJwFzgqWw_QFOQwXRjB0pisvLmXCR1YUnUgWPZqA@mail.gmail.com>
 <20130610021950.GA50356@icarus.home.lan>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
 (wonkity.com [127.0.0.1]); Sun, 09 Jun 2013 21:26:21 -0600 (MDT)
Cc: freebsd-fs@freebsd.org, "Reed A. Cartwright" <cartwright@asu.edu>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Jun 2013 03:26:24 -0000

On Sun, 9 Jun 2013, Jeremy Chadwick wrote:

> On Sun, Jun 09, 2013 at 01:25:47PM -0700, Reed A. Cartwright wrote:
>> Thanks, it makes sense now.
>>
>> Would it make sense to have a script that processes the output of "cam
>> devlist -v" to produce such an example output?
>>>
...
>
> The script would be ugly and require one-offs per driver.  For example,
> look at your "camcontrol devlist -v" output with regards to mps1 and
> mps2.  There's no indication of what the bus #, target #, or lun #
> should be because there are no disks on the controller.  I made an
> educated guess based off of mps0/mps3 and previous familiarity (on the
> lists -- I've never used one of these controllers) with mps(4).
>
> Had you shown me "camcontrol devlist -v" output with only 1 controller
> and 1 disk, I would have had to go purely off of what I've seen in the
> past.

This all looks remarkably complicated and fragile compared to labels.