Hi GC, keeping track of changed blocks is implemented using bitmaps, which are part of the meta data on both sides. These bitmaps are always of full size, so they will not grow by just changing blocks.
So unless you added something consuming ressources, e.g. event handlers performing LVM snapshots to be created when the peers disconnect, a single peer may run infinite. Best regards, // Veit Am Donnerstag, den 14.06.2018, 19:07 -0500 schrieb G C: > I know the secondary is the DR and the primary keeps track of what is > changing but how long can it continue to run in this state before it will > cause it to crash or not be writable any longer? I would gather that at > some point it would cause a lack of resources to write the changes to but > I'm not sure and can't find any information related to it. > _______________________________________________ > drbd-user mailing list > drbd-user@lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user _______________________________________________ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
