Got error 128 when reading "Table Name" - when i tried to truncate a partition in a table

When I was trying to truncate a partition i received the following error
2019-05-28 4:47:50 24189 [ERROR] Got error 128 when reading table '.\datafactorydb\rjis_jqi_perf'

I am on Windows 2008 R1, 32-bit

the statement
alter table rjis_jqi_perf truncate partition p20 just hangs; and then I get the above error 128 in the mariadb log file.

I cancel the statement; and retry 5minutes later and still the same problem.

I tried a third time and the statement worked.

The statements I was running on a large table was (all worked first time except it hung on P20):-
alter table rjis_jqi_perf truncate partition p1;
alter table rjis_jqi_perf truncate partition p2;
alter table rjis_jqi_perf truncate partition p3;
alter table rjis_jqi_perf truncate partition p4;
alter table rjis_jqi_perf truncate partition p5;
alter table rjis_jqi_perf truncate partition p6;
alter table rjis_jqi_perf truncate partition p7;
alter table rjis_jqi_perf truncate partition p8;
alter table rjis_jqi_perf truncate partition p9;
alter table rjis_jqi_perf truncate partition p10;
alter table rjis_jqi_perf truncate partition p11;
alter table rjis_jqi_perf truncate partition p12;
alter table rjis_jqi_perf truncate partition p13;
alter table rjis_jqi_perf truncate partition p14;
alter table rjis_jqi_perf truncate partition p15;
alter table rjis_jqi_perf truncate partition p16;
alter table rjis_jqi_perf truncate partition p17;
alter table rjis_jqi_perf truncate partition p18;
alter table rjis_jqi_perf truncate partition p19;
alter table rjis_jqi_perf truncate partition p20;
alter table rjis_jqi_perf truncate partition p21;
alter table rjis_jqi_perf truncate partition p22;
alter table rjis_jqi_perf truncate partition p23;
alter table rjis_jqi_perf truncate partition p24;
alter table rjis_jqi_perf truncate partition p25;
alter table rjis_jqi_perf truncate partition p29;
alter table rjis_jqi_perf truncate partition p30;
alter table rjis_jqi_perf truncate partition p31;

Not sure if this relates to the bug in MDEV-17877