Elliptics has self-recovery mechanism on read.
Let's suppose that client reads data from groups 1, 2 and 3. And group 1 returned “no such file or directory” error but read from group 2 was successful. Then Elliptics writes recently read data from group 2 to group 1 with correct timestamp, data and user_flags. Writing is performed asynchronously, so read result is returned as it is ready nevertheless how long write operation is.