Date: Sun, 9 Jun 2013 21:26:21 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Jeremy Chadwick <jdc@koitsu.org> Cc: freebsd-fs@freebsd.org, "Reed A. Cartwright" <cartwright@asu.edu> Subject: Re: ZFS and Glabel Message-ID: <alpine.BSF.2.00.1306092122550.75158@wonkity.com> In-Reply-To: <20130610021950.GA50356@icarus.home.lan> References: <CALOkxuzH81UFuVZifJNxyuo6%2Bhu9mCPB1TC91dn5fkjVLFqTKw@mail.gmail.com> <CALOkxuxb0HBMXOwP6Z4JjvBk%2BbtnriCeCdhcKfmP=FyNEaseTA@mail.gmail.com> <CALOkxuxT9Oko1jm40GzYZbcTNu4epNgh8BoVhc-cH2UKNNbSvw@mail.gmail.com> <20130609065430.GA28206@icarus.home.lan> <CALOkxuwVDYmJwFzgqWw_QFOQwXRjB0pisvLmXCR1YUnUgWPZqA@mail.gmail.com> <20130610021950.GA50356@icarus.home.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1306092122550.75158>