Hi All, Currently I see that almost all the xlators in glusterfs do not handle EAGAIN/EBUSY errors.
Though this should be handled by the applications, there are multiple paths where the op's are not performed by the applications (but are internal to glusterfs). Few of these are a. Rebalance b. Replace brick c. Self-heal d. lk's etc... With the proposed snap feature (http://www.gluster.org/community/documentation/index.php/Features/snapshot), would it not be better to identify such op's inside glusterfs? Irrespective of the snap feature, I think it is about correctness to handle EAGAIN/EBUSY in these code paths. Please comment. With regards, Shishir _______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
