comments far below...
On May 22, 2012, at 1:42 AM, Jim Klimov wrote:
> 2012-05-22 7:30, Daniel Carosone wrote:
>> On Mon, May 21, 2012 at 09:18:03PM -0500, Bob Friesenhahn wrote:
>>> On Mon, 21 May 2012, Jim Klimov wrote:
This is so far a relatively raw idea and I've probably missed
som
2012-05-23 20:54, Richard Elling wrote:
comments far below...
Thank you Richard for taking notice of this thread and the
definitive answers I needed not quote below, for further
questions ;)
2) How did you "treat errors as expected" during scrub?
As I've discovered, there were hoops to jump t
On May 23, 2012, at 1:32 PM, Jim Klimov wrote:
> 2012-05-23 20:54, Richard Elling wrote:
>> comments far below...
>
> Thank you Richard for taking notice of this thread and the
> definitive answers I needed not quote below, for further
> questions ;)
>
>>> 2) How did you "treat errors as expecte
Thanks again,
2012-05-24 1:01, Richard Elling wrote:
At least the textual error message infers that if a hotspare
were available for the pool, it would kick in and invalidate
the device I am scrubbing to update into the pool after the
DD-phase (well, it was not DD but a hung-up resilver in this
On Thu, May 17, 2012 at 2:50 PM, Jim Klimov wrote:
> New question: if the snv_117 does see the 3Tb disks well,
> the matter of upgrading the OS becomes not so urgent - we
> might prefer to delay that until the next stable release
> of OpenIndiana or so.
There were some pretty major fixes and new
On May 23, 2012, at 2:56 PM, Jim Klimov wrote:
> Thanks again,
>
> 2012-05-24 1:01, Richard Elling wrote:
>>> At least the textual error message infers that if a hotspare
>>> were available for the pool, it would kick in and invalidate
>>> the device I am scrubbing to update into the pool after
