Re: [DRBD-user] BAD! .... messages
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 be fixed, finally... > UNQUOTE > I'm running 8.9 ... is this still something I can safely ignore (and not > fixed)? No, you are NOT running drbd 8.9. That's the version of the userland tools. You want to check (and upgrade) your kernel module. Check: modinfo drbd; head /proc/drbd >>> Ok. I'm running kernel module 8.4.3 with 8.9 userland tools: >>> >>> root@ns8p2:~# modinfo drbd >>> filename: >>> /lib/modules/3.16.0-4-amd64/kernel/drivers/block/drbd/drbd.ko >>> alias: block-major-147-* >>> license:GPL >>> version:8.4.3 >>> >>> ... is this still something I can safely ignore (and not fixed)? >> We are back at what Lars said: "You want to check (and upgrade) your >> kernel module.". Don't miss the upgrade part just because it is in >> parentheses. Out-of-tree 8.4.3 was February *2013*. > Uhm, so the ML post quoted above said "8.3 git" finally fixed "it". > > Which is correct. Only that "it" was something different than what > you have with 8.4.3 ... > > Even though it leads to similar messages in the kernel log. > > BTW, for people finding this in the archives: > we have *different* log lines that prominently contain "BAD", > so just because you see "BAD" does not yet mean you are seeing > the same issue. This one is about > "BAD! sector=12345s enr=6 rs_left=-7 rs_failed=0 count=89 cstate=..." > > We've had various issues over the years that would trigger those > log messages, some could safely be ignored, some could lead to > resync not terminating, or other effects. > > I'd recommend to not ignore those, but upgrade to latest 8.4. > Yes, these issues are (supposed to be) fixed, > the one I suspect you are hitting was fixed with > 1c378ef drbd: fix resync finished detection > Which was somewhere between 8.4.4 and 8.4.5 in 2014, and yes, it was a > different issue from the one referred to in the ML post you found. I replied to Roland's post before reading yours... Thanks for answering the question I asked in my reply to Roland which is to which version I should upgrade: latest 8.4 = 8.4.9.1 If these log messages can't be ignored, I suppose BAD! = bad. Should I file a bug against the Debian kernel for including a drbd module with known potentially BAD! (pun intended ;-) ) bugs or is that something you'd normally do? kind regards, Jan ___ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
Re: [DRBD-user] BAD! .... messages
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, action=close 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 to update/reinitialize it at some stage. Depending on your exact DRBD version, I could tell you various things about this. But if you run 8.3 git it is supposed to be fixed, finally... > /It seems to have completed the synchronization successfully. Also, no "read errors" where />/reported in on either host. />//>/Should I be concerned about the data integrity, now? / Nope. All good. UNQUOTE root@ns8p2:~# dpkg --list | grep drbd ii drbd-utils 8.9.2~rc1-2+deb8u1 amd64 RAID 1 over TCP/IP for Linux (user utilities) root@ns8p2:~# I'm running 8.9 ... is this still something I can safely ignore (and not fixed)? >>> No, you are NOT running drbd 8.9. That's the version of the userland tools. >>> >>> You want to check (and upgrade) your kernel module. >>> Check: modinfo drbd; head /proc/drbd >> Ok. I'm running kernel module 8.4.3 with 8.9 userland tools: >> >> root@ns8p2:~# modinfo drbd >> filename: >> /lib/modules/3.16.0-4-amd64/kernel/drivers/block/drbd/drbd.ko >> alias: block-major-147-* >> license:GPL >> version:8.4.3 >> >> ... is this still something I can safely ignore (and not fixed)? > We are back at what Lars said: "You want to check (and upgrade) your > kernel module.". Don't miss the upgrade part just because it is in > parentheses. Out-of-tree 8.4.3 was February *2013*. I didn't miss the "upgrade part" but needed a little time to get my head around that. I've used Debian for years and have come to rely on the "rock solid" reputation as advertised as well as personally experienced. It's not feasible (for me) to know all intricate details of kernel versions and (in)compatible modules or drivers, instead I'm relying on the great work the Debian community (and you guys!) do. I'm using the current Debian stable assuming (wrongly perhaps?) that that would give me a stable operating platform with software (kernel, userland etc) all from the stable repositories. Debian Jessie apparently packages kernel module 8.4.3 with userland tools 8.9.2~rc1-2+deb8u1. Are you saying that the Debian kernel maintainers missed including a required / important / critical update to the drbd kernel module in the stock kernel shipped with Debian Jessie? If so, are you advising to upgrade the kernel as well as the drbd kernel module? Or are you advising to only upgrade the drbd kernel module? If so to which version should I upgrade it? According to https://www.drbd.org/en/doc/users-guide-84/s-upgrading-drbd, I need to obtain a hash from Linbit support if I want to use the Linbit provided packages for Debian. Would that upgrade the Debian maintained kernel to a Linbit maintained kernel? What is required to obtain the hash? kind regards, Jan -- Omiha Systems Ltd NEW ZEALAND For support please email supp...@omiha.com or browse to http://support.omiha.com For urgent support please call p +64 9 950 3007 m +64 22 103 9151 m +64 22 1984 064 m +64 22 312 5916 ___ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
Re: [DRBD-user] BAD! .... messages
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 be fixed, finally... > > >> UNQUOTE > > >> I'm running 8.9 ... is this still something I can safely ignore (and not > > >> fixed)? > > > No, you are NOT running drbd 8.9. That's the version of the userland > > > tools. > > > > > > You want to check (and upgrade) your kernel module. > > > Check: modinfo drbd; head /proc/drbd > > > > Ok. I'm running kernel module 8.4.3 with 8.9 userland tools: > > > > root@ns8p2:~# modinfo drbd > > filename: > > /lib/modules/3.16.0-4-amd64/kernel/drivers/block/drbd/drbd.ko > > alias: block-major-147-* > > license:GPL > > version:8.4.3 > > > > ... is this still something I can safely ignore (and not fixed)? > > We are back at what Lars said: "You want to check (and upgrade) your > kernel module.". Don't miss the upgrade part just because it is in > parentheses. Out-of-tree 8.4.3 was February *2013*. Uhm, so the ML post quoted above said "8.3 git" finally fixed "it". Which is correct. Only that "it" was something different than what you have with 8.4.3 ... Even though it leads to similar messages in the kernel log. BTW, for people finding this in the archives: we have *different* log lines that prominently contain "BAD", so just because you see "BAD" does not yet mean you are seeing the same issue. This one is about "BAD! sector=12345s enr=6 rs_left=-7 rs_failed=0 count=89 cstate=..." We've had various issues over the years that would trigger those log messages, some could safely be ignored, some could lead to resync not terminating, or other effects. I'd recommend to not ignore those, but upgrade to latest 8.4. Yes, these issues are (supposed to be) fixed, the one I suspect you are hitting was fixed with 1c378ef drbd: fix resync finished detection Which was somewhere between 8.4.4 and 8.4.5 in 2014, and yes, it was a different issue from the one referred to in the ML post you found. -- : Lars Ellenberg : LINBIT | Keeping the Digital World Running : DRBD -- Heartbeat -- Corosync -- Pacemaker DRBD® and LINBIT® are registered trademarks of LINBIT __ please don't Cc me, but send to list -- I'm subscribed ___ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
Re: [DRBD-user] DRBD9 daemon not started at startup
On Mon, Nov 21, 2016 at 01:59:43AM +0100, Jasmin J. wrote: > Hi! > > > It is a kernel module not a process. > THX for answering! > > Just after reboot I get: > root@hasi:/etc/lvm# drbdsetup status --verbose --statistics > # No currently configured DRBD found. > > Then I do: > root@hasi:/etc/lvm# drbdadm up vm_disk_hasi > And then it is present. As expected. If nobody does the "up", it is not up. > >> What is the intended procedure to start this service? > So again my question, which software needs to do "drbdadm up .."? That depends on your setup. - Maybe it is you or your favorite admin via the command line - Maybe it is the init script - Maybe it is drbdmanage - Maybe it is the cluster manager. But for sure you don't want to mix these. > How should this be done in Proxmox 4.3? Personally, I have no clue, the Proxmox docs/MLs might be more appropriate, but I have seen some Proxmoxers here too... Regards, rck ___ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
Re: [DRBD-user] BAD! .... messages
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, > >> > >> 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 to update/reinitialize it at some stage. > >> > >> Depending on your exact DRBD version, I could tell you various things > >> about this. But if you run 8.3 git it is supposed to be fixed, finally... > >> > >>> /It seems to have completed the synchronization successfully. Also, no > >> "read errors" where />/reported in on either host. />//>/Should I be > >> concerned about the data integrity, now? / > >> Nope. All good. > >> > >> UNQUOTE > >> > >> root@ns8p2:~# dpkg --list | grep drbd > >> > >> ii drbd-utils 8.9.2~rc1-2+deb8u1 amd64 > >> RAID 1 over TCP/IP for Linux (user utilities) > >> > >> root@ns8p2:~# > >> > >> > >> I'm running 8.9 ... is this still something I can safely ignore (and not > >> fixed)? > > No, you are NOT running drbd 8.9. That's the version of the userland tools. > > > > You want to check (and upgrade) your kernel module. > > Check: modinfo drbd; head /proc/drbd > > Ok. I'm running kernel module 8.4.3 with 8.9 userland tools: > > root@ns8p2:~# modinfo drbd > filename: > /lib/modules/3.16.0-4-amd64/kernel/drivers/block/drbd/drbd.ko > alias: block-major-147-* > license:GPL > version:8.4.3 > > ... is this still something I can safely ignore (and not fixed)? We are back at what Lars said: "You want to check (and upgrade) your kernel module.". Don't miss the upgrade part just because it is in parentheses. Out-of-tree 8.4.3 was February *2013*. Regards, rck ___ drbd-user mailing list drbd-user@lists.linbit.com http://lists.linbit.com/mailman/listinfo/drbd-user
