Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hi Veit, > On 9/10/2017, at 11:07 PM, Veit Wahlich <cru.lists at zodia.de> wrote: > > Hi Jan, > > Am Sonntag, den 08.10.2017, 13:07 +1300 schrieb Jan Bakuwel: >> I'd like to include an automatic disconnect/connect on the secondary if >> out-of-sync blocks were found but so far I haven't found out how I can >> query drbd to find out (apart from parsing the log somehow). I hope >> there's a simpler/cleaner way to find out. > > beside it is wise to monitor for OOS blocks using methods like those > suggested by Robert, IMO it is advisable to NOT sync OOS blocks > automatically as it usually indicates a problem with your storage stack > or its configuration. Good point, thanks. I've seen OOS blocks in the past where storage stack appeared to be fine (hardware wise). What possible causes could there be? Hardware issues, bugs in storage stack including DRBD itself, network issues. In most (all?) cases it seems prudent to me to keep the resources in sync as much as possible and of course investigate once alerted by the monitoring system. best regards, Jan