MilkyWay@Home N-Body Sim. - Exit status 196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED

de_nbody_8_22_16_v162_2k_1_1472577603_750574
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1300435691

de_nbody_8_22_16_v162_2k_1_1472577603_1010655
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1304727954


[EDIT:
de_nbody_8_22_16_v162_2k_1_1472577603_1004517
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1304616435

de_nbody_8_1_16_v162_2k_3_1472577603_1016213
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=1304838530]



In the BOINC/Messages are:
Aborting task xxxxxx: exceeded disk limit: xx.xxMB > 50.00MB


Is this something an admin need to look?

Maybe there is a workaround via cc_config.xml file (or an other way) possible?


Thanks.

---

I just had the same thing happen to me a few minutes ago. Someone seriously needs to look at this problem.

9/15/2016 2:03:46 PM | Milkyway@Home | Aborting task de_nbody_8_22_16_v162_2k_2_1473877202_152040_1: exceeded disk limit: 169.05MB > 50.00MB

9/15/2016 1:33:43 PM | Milkyway@Home | Aborting task de_nbody_9_14_16_v162_2k_25bins__1_1473877202_159175_0: exceeded disk limit: 181.77MB > 50.00MB

Hey,

Sidd knows about the problem and has been looking into it for a while. Not sure on his progress. Hopefully he will have a fix for it in one of the next releases.

Jake

I liked to let run the N-body WUs on the CPUs, but with an error rate of ~ 50 % it's... ahh... not so 'nice'... - so I stopped crunching N-body WUs...

---

Hm, it's not so nice to let run still the 1.62 N-body app (send out WUs) - and a very high percentage of the results finish with an error...

When will be released a new app, so it's again meaningful to let run N-body WUs?

Thanks.

---