On Tuesday 16 June 2015 02:19 AM, Emmanuel Dreyfus wrote:
Rajesh Joseph <rjos...@redhat.com> wrote:
Correct me if I am wrong, but I think interruptible is good with hard
mount. Which is good in real deployment scenario. Since we are talking
about test scripts, I thought soft mount along with timeout period can be
a good option to prevent hangs.
soft mount means an I/O operation can timeout and return failure
interruptible mount means you can kill a process undergoing I/O, which
is useful for cleanup routine.
Both are like belt with sustenders, but given how likely we are to hang,
it does not hurts.
We again hit this problem [1]. Can we use soft mount with some retries
and timeouts so that we don't need manual intervention to recover a hung VM?
Thanks,
Vijay
[1]
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/6971/console
_______________________________________________
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
