Re: [DRBD-user] cronjob for verify

Hi Jan, Am Dienstag, den 10.10.2017, 13:11 +1300 schrieb Jan Bakuwel: > Thanks for that. Must say that possibility has escaped my attention so > far. I'm using DRBD in combination with Xen and LVM for VMs so I assume > O_DIRECT is in play here. Any suggestions where to go from here? A > search

Re: [DRBD-user] cronjob for verify

On 2017-10-10 13:11, Jan Bakuwel wrote: Hi Veit, On 10/10/17 08:47, Veit Wahlich wrote: Hi Jan, Am Dienstag, den 10.10.2017, 06:56 +1300 schrieb Jan Bakuwel: I've seen OOS blocks in the past where storage stack appeared to be fine (hardware wise). What possible causes could there be?

Re: [DRBD-user] cronjob for verify

Hi Veit, On 10/10/17 08:47, Veit Wahlich wrote: Hi Jan, Am Dienstag, den 10.10.2017, 06:56 +1300 schrieb Jan Bakuwel: 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

Re: [DRBD-user] cronjob for verify

Hi Jan, Am Dienstag, den 10.10.2017, 06:56 +1300 schrieb Jan Bakuwel: > 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?)

Re: [DRBD-user] cronjob for verify

Hi Veit, > On 9/10/2017, at 11:07 PM, Veit Wahlich 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

Re: [DRBD-user] cronjob for verify

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 >

[DRBD-user] cronjob for verify

Hi, I'm periodically verifying all DRBD volumes with a cronjob. The manual states "If out-of-sync blocks are found, they are not resynchronized automatically. To do that, disconnect and connect the resource when verification has completed." I'd like to include an automatic