On Sun, Jun 07, 2015 at 05:19:41PM +0200, Paolo Quinci wrote: > Dear all! > I configured two nodes with corosync and DRBD 8.4 on Ubuntu Server > 14.04.02 LTS. After I updated the Kernel on both nodes the nodes > cannot sync anymore. I tried to downgrade to the lastest still > working kernel without success. The sync process starts and ends with > a message saying "BAD! BarrierACK received #432, expected #431". I
That's a sign for re-ordering. May be a bug in DRBD; may be a bug in lower level drivers or the IO backend. May be a configuration bug. Risk: *potential* data corruption. > looked up the error but it seems to be an error not many run into. Now > I really don't know what to do anymore. Maybe someone of you can help > me. The two nodes now work in a production environment, so starting > from scratch is not an option I have to add. Backups of the data on > the DRBD device are being made on a daily basis though. My > setup:Kernel: 3.13.0-53-generic #89-Ubuntu SMP Wed May 20 10:34:39 UTC > 2015 x86_64 x86_64 x86_64 GNU/LinuxDRBD:DRBDADM_BUILDTAG=GIT-hash:\ > 599f286440bd633d15d5ff985204aff4bccffadd\ build\ by\ phil@fat-tyre\,\ > 2013-10-11\ > 16:42:48DRBDADM_API_VERSION=1DRBD_KERNEL_VERSION_CODE=0x080403DRBDADM_VERSION_CODE=0x080404DRBDADM_VERSION=8.4.4 Use a DRBD more recent than 2013? DRBD 8.4.6 maybe? Cheers, -- : Lars Ellenberg : http://www.LINBIT.com | Your Way to High Availability : DRBD, Linux-HA and Pacemaker support and consulting DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed _______________________________________________ drbd-user mailing list [email protected] http://lists.linbit.com/mailman/listinfo/drbd-user
