Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Florian -- Thanks for the clarification! Is that true with older versions of DRBD as well (e.g. 0.7.23)? Ron Blechman | Distinguished Member of Technical Staff | Avaya | 307 Middletown Lincroft Road | Room 3K-305 | Lincroft, NJ 07738 | Voice 732.852.2310 | Fax 732.852.1375 | rblechman at avaya.com -----Original Message----- From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Florian Haas Sent: Monday, November 26, 2007 11:01 AM To: drbd-user at lists.linbit.com Subject: Re: [DRBD-user] Preventing initial full sync on new install On Monday 26 November 2007 16:28:17 Blechman, Ronald I, Jr (Ron) wrote: > "this" = whether one can actually write to the disk while > synchronization is in process. > > Perhaps the confusion is with the word "usable"..... does "usable" mean > "read and write" or just "read"? > > My assumption was with at least protocol C that the system is blocking > until the writes / synchronization has completed. That assumption is incorrect. You can read from and write to the device immediately. Block-by-block replication on the one hand and background sync on the other will run in parallel. You can even switch roles and make a not-yet-synced device Primary, in which case it will fetch as-yet-unsynced blocks over the wire, from the node that has a complete set of good data, and read already-synced blocks locally. As long as a network connection between the two is available, that is. And this is not dependent on the protocol you use. Cheers, Florian -- : Florian G. Haas : LINBIT Information Technologies GmbH : Vivenotgasse 48, A-1120 Vienna, Austria _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user