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

2017-09-25 Thread Eddie Chapman
On 25/09/17 22:02, Eric Robinson wrote: Problem: Under high write load, DRBD exhibits data corruption. In repeated tests over a month-long period, file corruption occurred after 700-900 GB of data had been written to the DRBD volume. Testing Platform: 2 x Dell PowerEdge R610 servers 32GB

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

2017-09-25 Thread Eric Robinson
Problem: Under high write load, DRBD exhibits data corruption. In repeated tests over a month-long period, file corruption occurred after 700-900 GB of data had been written to the DRBD volume. Testing Platform: 2 x Dell PowerEdge R610 servers 32GB RAM 6 x Samsung SSD 840 Pro 512GB (latest fir

Re: [DRBD-user] Problem updating 8.3.16 to 8.4.10 -- actually problem while *downgrading* (no valid meta-data signature found)

2017-09-25 Thread Lars Ellenberg
On Mon, Sep 25, 2017 at 01:25:34PM -0400, Digimer wrote: > On 2017-09-25 07:28 AM, Lars Ellenberg wrote: > > On Sat, Sep 23, 2017 at 11:32:42PM -0400, Digimer wrote: > >> I tried updating an 8.3.19 DRBD install (on EL6.9), and when I tried to > > > > 8.3.16 is the latest I know... typo I assume. >

Re: [DRBD-user] Problem updating 8.3.16 to 8.4.10 -- actually problem while *downgrading* (no valid meta-data signature found)

2017-09-25 Thread Digimer
On 2017-09-25 07:28 AM, Lars Ellenberg wrote: > On Sat, Sep 23, 2017 at 11:32:42PM -0400, Digimer wrote: >> I tried updating an 8.3.19 DRBD install (on EL6.9), and when I tried to > > 8.3.16 is the latest I know... typo I assume. Yup, typo. Was late... >> connect the updated node to the older no

Re: [DRBD-user] Problem updating 8.3.16 to 8.4.10 -- actually problem while *downgrading* (no valid meta-data signature found)

2017-09-25 Thread Lars Ellenberg
On Sat, Sep 23, 2017 at 11:32:42PM -0400, Digimer wrote: > I tried updating an 8.3.19 DRBD install (on EL6.9), and when I tried to 8.3.16 is the latest I know... typo I assume. > connect the updated node to the older node, I got this error: > > ==[ old node ]== > Sep 23 23:13:47 an-a02n02 kernel