Welcome to MilkyWay@home

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

Message boards : Number crunching : MilkyWay@Home N-Body Sim. - Exit status 196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Sutaru Tsureku

Send message
Joined: 30 Apr 09
Posts: 99
Credit: 29,853,513
RAC: 1,056
Message 65132 - Posted: 11 Sep 2016, 20:06:54 UTC
Last modified: 11 Sep 2016, 20:17:46 UTC

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.
ID: 65132 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
rcthardcore

Send message
Joined: 30 Dec 08
Posts: 30
Credit: 6,999,702
RAC: 0
Message 65150 - Posted: 15 Sep 2016, 18:38:10 UTC

I just had the same thing happen to me a few minutes ago. Someone seriously needs to look at this problem.
ID: 65150 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
rcthardcore

Send message
Joined: 30 Dec 08
Posts: 30
Credit: 6,999,702
RAC: 0
Message 65151 - Posted: 15 Sep 2016, 19:22:54 UTC

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
ID: 65151 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 25 Feb 13
Posts: 580
Credit: 94,200,158
RAC: 0
Message 65283 - Posted: 26 Sep 2016, 16:59:53 UTC

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
ID: 65283 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Sutaru Tsureku

Send message
Joined: 30 Apr 09
Posts: 99
Credit: 29,853,513
RAC: 1,056
Message 65296 - Posted: 26 Sep 2016, 21:57:30 UTC

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...
ID: 65296 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profile Sutaru Tsureku

Send message
Joined: 30 Apr 09
Posts: 99
Credit: 29,853,513
RAC: 1,056
Message 65386 - Posted: 5 Oct 2016, 18:07:59 UTC - in response to Message 65283.  

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.
ID: 65386 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : MilkyWay@Home N-Body Sim. - Exit status 196 (0xc4) EXIT_DISK_LIMIT_EXCEEDED

©2024 Astroinformatics Group