|author||kshithijiyer <firstname.lastname@example.org>||2019-11-05 15:28:34 +0530|
|committer||Bala Konda Reddy M <email@example.com>||2019-12-17 06:46:34 +0000|
[TC] Adding tc to verify data corruption during full heal with reboot.
This test case verifies that disruption during full heal doesn't result in data corruption. Testcase steps: 1.Create IO from mountpoint. 2.Calculate arequal from mount. 3.Delete data from backend from the EC volume. 4.Trigger heal full. 5.Disable Heal. 6.Again Enable and do Heal full. 7.Reboot a Node. 8.Calculate arequal checksum and compare it. Change-Id: I1fac53df30106ff98fdd270b210aca90a53a1ac5 Co-authored-by: Sunil Kumar Acharya <firstname.lastname@example.org> Signed-off-by: Sunil Kumar Acharya <email@example.com> Signed-off-by: Karan Sandha <firstname.lastname@example.org> Signed-off-by: kshithijiyer <email@example.com>
Diffstat (limited to 'glustolibs-gluster/glustolibs')
0 files changed, 0 insertions, 0 deletions