Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
No, the "dirty" bits are on disk. You can run degraded forever (or until the disk fails). The sync upon reconnect will still be much shorter than a full sync (unless the bitmap turns to x'FFFFFF's<g>). Dan -----Original Message----- From: drbd-user-bounces at lists.linbit.com [mailto:drbd-user-bounces at lists.linbit.com] On Behalf Of Digimer Sent: Thursday, March 03, 2011 10:13 AM To: Robinson, Eric Cc: drbd-user at lists.linbit.com Subject: Re: [DRBD-user] How Long Can a Primary Stay Disconnected from a Secondary? On 03/03/2011 10:05 AM, Robinson, Eric wrote: > I am thinking about taking a secondary node offline for maintenance > during production hours. I assume it cannot stay offline forever > because eventually the primary would run out of space to record > changes that need to be sync'd. Is there a way to know in advance how > long it is safe to stay disconnected without resync'ing? As I understand it, dirty blocks are recorded in memory. I am sure there is an upper limit to the counters, but I would hazard a guess that you would run out of RAM first. That said, I'd love to see some math from a DRBD developer. :) -- Digimer E-Mail: digimer at alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org _______________________________________________ drbd-user mailing list drbd-user at lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4993 bytes Desc: not available URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20110303/820c1e05/attachment.bin>