Brad Plecs wrote:
>> Are you sure this isn't a case of CR 6433264 which
>> was fixed
>> long ago, but arrived in patch 118833-36 to Solaris
>> 10?
>>
>
> It certainly looks similar, but this system already had 118833-36 when the
> error occurred, so if this bug is truly fixed, it must be some
> Are you sure this isn't a case of CR 6433264 which
> was fixed
> long ago, but arrived in patch 118833-36 to Solaris
> 10?
It certainly looks similar, but this system already had 118833-36 when the
error occurred, so if this bug is truly fixed, it must be something else. Then
again, I wasn't
Brad Plecs wrote:
> Problem solved... after the resilvers completed, the status reported that the
> filesystem needed an upgrade.
>
> I did a zpool upgrade -a, and after that completed and there was no
> resilvering going on, the zpool add ran successfully.
>
> I would like to suggest, however,
Problem solved... after the resilvers completed, the status reported that the
filesystem needed an upgrade.
I did a zpool upgrade -a, and after that completed and there was no resilvering
going on, the zpool add ran successfully.
I would like to suggest, however, that the behavior be fixed --
