Bugs and currupted plots

Only wrote 100224 of 271882 bytes at offset 872396928 to “/mnt/nvme0/plot-k32-2021-06-02-10-39-a07bcf38ceab37cfb102db5db972e8050de3198bc20e963b835842384ec2b8f7.plot.p1.t3.sort_bucket_000.tmp” with length 872497152. Error 1. Retrying in five minutes.
Forward propagation table time: 34639.804 seconds. CPU (5.570%) Wed Jun 2 23:06:10 2021
Computing table 4
Bucket 0 uniform sort. Ram: 3.840GiB, u_sort min: 3.250GiB, qs min: 0.813GiB.
terminate called after throwing an instance of ‘InvalidStateException’
what(): Offset too large: 3777
Aborted (core dumped)

I am getting that error few times… the beauty of unsafe C++. Then memory issue:

Starting phase 3/4: Compression from tmp files into “/mnt/nvme0/plot-k32-2021-06-02-10-50-746e88951445bb61f7c5460a2c5ddd2daafecd61f34c820ff43464cbac591efe.plot.2.tmp” … Thu Jun 3 12:20:45 2021
Compressing tables 1 and 2
Caught plotting error: Not enough memory for sort in memory. Need to sort 4.902759GiB
Traceback (most recent call last):
But I read we need to allocate only 3.6GiB, so why it needs 4.9?

I am also finding corrupted plots, like 30/40 every day! I think farming/plotting is just a waste of time because the project is too bug ridden and completely unreliable. Plotting is nearly a full-time job too, without getting any coin as reward.

You don’t say anything about your gear, nor your plotting parameters, so hard to tell you anything, but AFAICT there are no significant bugs, and it’s reliable, never seen a corrupted plot in >650 of them, plus some coin. What little info from your errors show, might indicate lack of disk space, not enough memory per plot, in that order. Doesn’t sound too hard to rectify.

Sporadic plotting failure may also be a sign of bad hardware, usually memory, especially in a new PC that is untested. Running memtest86 could rule that out.

It’s either bad memory/timings and or incorrect OC of the CPU