[Drbd-dev] How Locking in GFS works...
lmb at suse.de
Fri Oct 8 14:55:44 CEST 2004
On 2004-10-08T14:32:09, Philipp Reisner <philipp.reisner at linbit.com> wrote:
> 3. Concurrent writes, high latency for data packets.
> The problem now is that N2 does can not detect that this was
> a concurrent write, since it got the ACK before the conflicting
> data packets comes in.
Uhm. I don't see how this can be a problem.
In this case, one write has logically happened before the other, and
from they don't overlap - the second write will simply wipe out the
first one, which seems fine?
> 5. New write while processing a write from the peer.
Sounds just like case 1.
Lars Marowsky-Brée <lmb at suse.de>
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
More information about the drbd-dev