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
Hi Richard,
Richard Elling wrote:
Karthik Krishnamoorthy wrote:
We did try with this
zpool set failmode=continue pool 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
Karthik Krishnamoorthy wrote:
We did try with this
zpool set failmode=continue pool 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 I/O
Hello All,
Summary:
cp command for mirrored zfs hung when all the disks in the mirrored
pool were unavailable.
Detailed description:
~
The cp command (copy a 1GB file from nfs to zfs) hung when all the disks
in the mirrored pool (both c1t0d9 and
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
Neil,
Thanks for the quick suggestion, the hang seems to happen even with the
zpool set failmode=continue pool 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
We did try with this
zpool set failmode=continue pool 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
