Karthik, did you ever file a bug or this? I'm experiencing the same hang and
wondering how to recover.
/Brian
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listi
Hi Richard,
Richard Elling wrote:
> Karthik Krishnamoorthy wrote:
>> We did try with this
>>
>> zpool set failmode=continue option
>>
>> and the wait option before pulling running the cp command and pulling
>> out the mirrors and in both cases there was a hang and I have a core
>> dump of the ha
Karthik Krishnamoorthy wrote:
> We did try with this
>
> zpool set failmode=continue option
>
> and the wait option before pulling running the cp command and pulling
> out the mirrors and in both cases there was a hang and I have a core
> dump of the hang as well.
>
You have to wait for the
We did try with this
zpool set failmode=continue option
and the wait option before pulling running the cp command and pulling
out the mirrors and in both cases there was a hang and I have a core
dump of the hang as well.
Any pointers to the bug opening process ?
Thanks
Karthik
On 10/15/08 2
On 10/15/08 23:12, Karthik Krishnamoorthy wrote:
> Neil,
>
> Thanks for the quick suggestion, the hang seems to happen even with the
> zpool set failmode=continue option.
>
> Any other way to recover from the hang ?
You should set the property before you remove the devices.
This should preve
Neil,
Thanks for the quick suggestion, the hang seems to happen even with the
zpool set failmode=continue option.
Any other way to recover from the hang ?
thanks and regards,
Karthik
On 10/15/08 22:03, Neil Perrin wrote:
> Karthik,
>
> The pool failmode property as implemented governs the be
Karthik,
The pool failmode property as implemented governs the behaviour when all
the devices needed are unavailable. The default behaviour is to wait
(block) until the IO can continue - perhaps by re-enabling the device(s).
The behaviour you expected can be achieved by "zpool set failmode=continu
