Thanks for your answer. Now it makes sense.
I guess you could do some optimization to avoid sending a barrier too often.
nicolae
On Fri, Sep 24, 2010 at 8:53 PM, Lars Ellenberg
wrote:
>
> DRBD's usage of barriers/cache flushes is to make sure
> we won't "forget" to resync parts that need to be
On Fri, Sep 24, 2010 at 11:12:35AM +0200, Nicolae Mihalache wrote:
> Hello,
>
> I've been reading about the barriers (no-disk-barrier option) in drbd.
> I understand that when the primary gets a IO completion notification,
> it will issue a barrier request (actually start a new epoch) to the
> sec
Hello,
I've been reading about the barriers (no-disk-barrier option) in drbd.
I understand that when the primary gets a IO completion notification,
it will issue a barrier request (actually start a new epoch) to the
secondary.
However, if the disk of the primary has a write cache, it will
immediat
