Re: [DRBD-user] Warning: Data Corruption Issue Discovered in DRBD 8.4 and 9.0

2017-10-16 Thread Jan Bakuwel
Hi Eric & Lars, Well, damn. As the program was supposedly reviewed by Samsung engineers as part of their efforts to diagnose the root cause of TRIM errors, it never occurred to me that it was that buggy. I can't thank you enough for finding that! The rollout of some new DRBD clusters has been

Re: [DRBD-user] cronjob for verify

2017-10-09 Thread Jan Bakuwel
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

2017-10-09 Thread Jan Bakuwel
Hi Veit, > On 9/10/2017, at 11:07 PM, Veit Wahlich <cru.li...@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 fou

Re: [DRBD-user] Antwort: cronjob for verify

2017-10-09 Thread Jan Bakuwel
Hi Robert, > On 9/10/2017, at 9:17 PM, robert.koe...@knapp.com wrote: > > Just parse /proc/drbd for lines with oos: where the number behind oos is > not 0 Thanks, that's easy :-) Jan > Von:Jan Bakuwel <jan.baku...@gmail.com> > An:drbd-user@lists.linbit.com >

[DRBD-user] cronjob for verify

2017-10-07 Thread Jan Bakuwel
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

[DRBD-user] Fwd: Re: BAD! .... messages

2016-11-22 Thread Jan Bakuwel
Apologies ... list wasn't CC-ed ... Hi Christoph, FYI Your packages install without issue on a fresh stock Debian Jessie (3.16), see below. I'll see if I can rig up a test lab with a couple of old servers and put this under a bit of load. That will take me a bit of time though, will keep you

Re: [DRBD-user] BAD! .... messages

2016-11-21 Thread Jan Bakuwel
Hi Lars, On 22/11/16 06:14, Lars Ellenberg wrote: > On Mon, Nov 21, 2016 at 09:31:54AM +0100, Roland Kammerer wrote: > I found the following in the archives > (http://lists.linbit.com/pipermail/drbd-user/2012-July/018751.html): > QUOTE > But if you run 8.3 git it is supposed to

Re: [DRBD-user] BAD! .... messages

2016-11-21 Thread Jan Bakuwel
Hi Roland, On 21/11/16 21:31, Roland Kammerer wrote: > On Sat, Nov 19, 2016 at 04:52:14PM +1300, Jan Bakuwel wrote: >> Hi Lars, >> >> On 19/11/16 03:05, Lars Ellenberg wrote: >>> On Thu, Nov 17, 2016 at 10:53:43PM +1300, Jan Bakuwel wrote: >>>> Hi, &g

Re: [DRBD-user] BAD! .... messages

2016-11-18 Thread Jan Bakuwel
Hi Lars, On 19/11/16 03:05, Lars Ellenberg wrote: > On Thu, Nov 17, 2016 at 10:53:43PM +1300, Jan Bakuwel wrote: >> Hi, >> >> I found the following in the archives >> (http://lists.linbit.com/pipermail/drbd-user/2012-July/018751.html): >> >> QUOTE >

[DRBD-user] BAD! .... messages

2016-11-17 Thread Jan Bakuwel
Hi, I found the following in the archives (http://lists.linbit.com/pipermail/drbd-user/2012-July/018751.html): QUOTE >/Now I wonder: What does drbd0 want to tell me with those "BAD! ..." messages? / It's just some reference counter that should not have gone negative, but did, because we forgot