Hi all, first, sorry for asking this again. I would really like to understand the code, so the following question is important for me.
How does read/write during recovery works exactly. I first though we can simply reject reads. For writes, we can reject them until we start object recovery. After that point we cache/log written data (but still reject reads). When we have received the whole object we merge it with write cache (apply write log). But code in request.c (request_in_recovery()) seems to delay such request, and put them on a wait queue. Why is that necessary? - Dietmar -- sheepdog mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/sheepdog
