Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
> > It can be one of the following three: > > > > C: write IO is reported as completed, if we know it has > > reached _both_ local and remote DISK. > > * for critical transactional data. > > * for most cases. Most ? > > B: write IO is reported as completed, if it has reached > > local DISK and remote buffer cache. > > * for cases were you can live with possible data loss > of the last few milliseconds in case of failover > > we should improve our documented recommendations :) > > > A: write IO is reported as completed, if it has reached > > local DISK and local tcp send buffer. (see also sndbuf-size) > > * for high latency networks > > > > If you choose C, then write a file to the DRBD'd filesystem, > > the write won't > > and then fsync! otherwise the write goes > just into the local nodes cache, > and drbd knows nothing about it yet... Do you bypass this requirement my mounting your filesystem sync ? Mark. -- Mark Watts BSc RHCE MBCS Senior Systems Engineer QinetiQ Trusted Information Management Trusted Solutions and Services Group GPG Key: http://keyserver.veridis.com:11371/search?q=0x455420ED -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20070510/be29ffa1/attachment.pgp>