Andrey Korolyov
2014-10-13 19:33:14 UTC
Hello,
since very long period (at least from cuttlefish) many users,
including me, experiences rare but still very disturbing client
crashes (#8385, #6480, and couple of other same-looking traces for
different code pieces, I may start the corresponding separate bugs if
necessary). The main problem is that the issues are very hard to
reproduce in a deterministic way, although they are *primarily*
correlate with disk workload.
Despite fixing all reported separately is a definitely a working way,
the issue can be also caused be simularly-behaving single piece of
code belonging to one of shared libraries. As issue touches more or
less all existing deployments on stable release, may be it is worthy
(and possible) to fix it not by cleaning up particular issues one by
one.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
since very long period (at least from cuttlefish) many users,
including me, experiences rare but still very disturbing client
crashes (#8385, #6480, and couple of other same-looking traces for
different code pieces, I may start the corresponding separate bugs if
necessary). The main problem is that the issues are very hard to
reproduce in a deterministic way, although they are *primarily*
correlate with disk workload.
Despite fixing all reported separately is a definitely a working way,
the issue can be also caused be simularly-behaving single piece of
code belonging to one of shared libraries. As issue touches more or
less all existing deployments on stable release, may be it is worthy
(and possible) to fix it not by cleaning up particular issues one by
one.
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html