[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#687380: marked as done (Please verify DRBD data corruption bug / patch)

Your message dated Sun, 16 Sep 2012 05:44:26 +0100
with message-id <1347770666.13258.249.camel@deadeye.wl.decadent.org.uk>
and subject line Re: Bug#687380: Please verify DRBD data corruption bug / patch
has caused the Debian Bug report #687380,
regarding Please verify DRBD data corruption bug / patch
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
687380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=687380
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-amd64
Severity: important

In their current newsletter, LINBIT states:


DRBD 8.4.2 Has been Released

For any user of DRBD-8.4, we suggest an upgrade to 8.4.2 as changes to the kernel in version 2.6.36 or newer have caused an issue that may cause data corruption on a Secondary/Sync target when using protocols A or B. (In the 8.3 series this was already fixed with the 8.3.13 release).

It is worth noting that all previous DRBD releases did not enforce correct ordering of (some) write operations on a resync-target node.   It is a rare condition that could trigger the potential data corruption. It may cause corruption in the sense that it looks like if a single block write was not executed on the secondary.  Actually it was overwritten with the previous version of the data.  This second write originates from the resync process.

Apart from that those nasty bugs, we have also fixed a condition where "disk-barrier no" and "disk-flushes no" were ineffective. This was the reason why some people were reporting "drbd-8.3 is faster than drbd-8.4".



Referenced GIT commit:
http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=tag;h=refs/tags/drbd-8.4.2

Please verify if this bug(fix) applies to any Debian maintained
kernel!

Thank you,
Raoul
--
____________________________________________________________________
DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia@ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OG          web.          http://www.ipax.at
Barawitzkagasse 10/2/2/11           email.            office@ipax.at
1190 Wien                           tel.               +43 1 3670030
FN 277995t HG Wien                  fax.            +43 1 3670030 15
____________________________________________________________________

--- End Message ---
--- Begin Message --- 
On Wed, 2012-09-12 at 11:40 +0200, Raoul Bhatia [IPAX] wrote:
> Package: linux-image-amd64
> Severity: important
> 
> In their current newsletter, LINBIT states:
> 
> > DRBD 8.4.2 Has been Released
> >
> > For any user of DRBD-8.4, we suggest an upgrade to 8.4.2 as changes to the kernel in version 2.6.36 or newer have caused an issue that may cause data corruption on a Secondary/Sync target when using protocols A or B. (In the 8.3 series this was already fixed with the 8.3.13 release).
> >
> > It is worth noting that all previous DRBD releases did not enforce correct ordering of (some) write operations on a resync-target node.   It is a rare condition that could trigger the potential data corruption. It may cause corruption in the sense that it looks like if a single block write was not executed on the secondary.  Actually it was overwritten with the previous version of the data.  This second write originates from the resync process.
> >
> > Apart from that those nasty bugs, we have also fixed a condition where "disk-barrier no" and "disk-flushes no" were ineffective. This was the reason why some people were reporting "drbd-8.3 is faster than drbd-8.4".
> 
> 
> Referenced GIT commit:
> http://git.drbd.org/gitweb.cgi?p=drbd-8.4.git;a=tag;h=refs/tags/drbd-8.4.2
> 
> Please verify if this bug(fix) applies to any Debian maintained
> kernel!

We don't track out-of-tree drivers.  If you can identify relevant bug
fixes in the mainline Linux kernel, please do so.

Ben.

-- 
Ben Hutchings
Experience is what causes a person to make new mistakes instead of old ones.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: