When the system (ProLiant DL360 Gen9, dual E5-2620 v4, 32 gigs ram, Nvidia P4, 75k C2 plots) hits a high IO load on the same block device as the Chia Full Node DB, shortly after the debug.log in chia will show GRResult not ok. The number of plots, lookup times, all seems fine - but the harvester stops finding proofs until the harvester is restarted. Happens 1-2 times in a 24 hour period on Alpha 4 through Alpha 4.3
Whenever error occurs, block validation time and lookup time consistently increase leading up to the error being thrown.
Reproducible with Nvidia Unix GPU Driver versions 530.30.03, 530.41.03, and 535.43.02
What new plot format? I don't see anything about it in this repo. Some better communication would be appreciated. Why would a new format fix the problem?
What happened?
When the system (ProLiant DL360 Gen9, dual E5-2620 v4, 32 gigs ram, Nvidia P4, 75k C2 plots) hits a high IO load on the same block device as the Chia Full Node DB, shortly after the debug.log in chia will show GRResult not ok. The number of plots, lookup times, all seems fine - but the harvester stops finding proofs until the harvester is restarted. Happens 1-2 times in a 24 hour period on Alpha 4 through Alpha 4.3
Whenever error occurs, block validation time and lookup time consistently increase leading up to the error being thrown.
Reproducible with Nvidia Unix GPU Driver versions 530.30.03, 530.41.03, and 535.43.02
Version
2.0.0b3.dev56
What platform are you using?
Ubuntu 22.04 Linux Kernel 5.15.0-73-generic ProLiant DL360 Gen9, dual E5-2620 v4, 32 gigs ram, Nvidia P4, 75k C2 plots
What ui mode are you using?
CLI
Relevant log output