And now this:

Thu 11 Oct 2018 10:10:44 AM CDT | GPUGRID | Aborting task 123_35_37_39_42_da3ae375_n00001-SDOERR_SELE6-0-1-RND5707_4: exceeded disk limit: 59944.94MB > 57220.46MB

Looks like the project admins need to make some adjustments.

Yes, I have also reluctantly set preferences not to accept any more production QC tasks until the disk usage problem is identified and eliminated. I had 6 machines with 16 threads (1/2 of available threads) on the project but all these WU's are just thrashing my machines and producing errors after an hour of so wasted cpu time. I am configured to run QC beta should any fixes be attempted.

Tried two more QC tasks, they all fail the same way. Complete silence from admins.
Tullio

Decided to give it a try again. Rough estimates are 1 valid for every 4 errors.

Almost all validates were after another computer errored out but not due to size limits.
So there are batches of work units out there that don't exceed the limit but failed for other reasons.

However, on my computers, almost all of my errors were size related. So the original error for this thread still exist.

---

Going back to Aug24, my QC completion record shows 194 errors out of 454 QC WU's processed. This is about a 42.7% failure rate and a small random sampling of the error causes reveals almost all due to 'disk usage limit exceeded.' Would be nice to get an explanation what specifically this error means.

I am running other 4 BOINC projects, both on Linux and Windows 10. Some use also GPUs, some don't but use Virtual Box, so I have a vast experience on all kind of errors. But all give me a feedback by admins or other volunteers with similar experiences. Here only silence.
Tullio

The error has occurred on some other projects where the disk size usage went past a limit set by the app. It wasn't a limit on the PC running the task.

of the few validating, this is the biggest so far

http://www.gpugrid.net/workunit.php?wuid=14584472

4943 seconds credit 1279.49

---

Ok I will ask Toni if he can increase the WU disk space. But at some point we will just write your whole disk full as it seems...

Ok I will ask Toni if he can increase the WU disk space. But at some point we will just write your whole disk full as it seems...

Thanks Stefan...

I increased my SSD to 500 GB so I'm good for now but It's always easier to clone the OS to a larger SSD than it is to a smaller SSD. If we start to hit a limit on the SSD then I guess I have an excuse to look at 1 T SSD hahaha...

---

We decided to cancel them for the moment. I might redesign it at a later point and send more sensible WUs out. Sorry for the trouble, I was a bit out these days working on finishing up a project.

I am making some new ones now to send out maybe by tomorrow.

I am making some new ones now to send out maybe by tomorrow.

Very good. But please don't compromise the project for that. I usually have at least 180 GB free these days with the 256 GB SSDs.
I know not everyone can do that, so you could try separating into small and large.

It's okay because we run two separate QM projects. So I'll stop the SELE WUs and restart the QMML ones but with larger batch sizes now to avoid spamming the conda server and getting blocked.

I received a notice from the server that QC tasks require 77 GB. But I have more than 700 GB available to BOINC on my two Linux boxen. No other BOINC project requires that much space.
Tullio

The new ones won't really require any disk space because they are smaller molecules. Although I don't know how BOINC does it, like if it reserves the maximum space per WU or it just cuts the WU if it exceeds the max space.

I received a notice from the server that QC tasks require 77 GB. But I have more than 700 GB available to BOINC on my two Linux boxen. No other BOINC project requires that much space.
Tullio

There is a disk size limit set by the server for tasks. The error is not that your own physical disk is out of space. The task filled its allotted amount of space.

The new ones won't really require any disk space because they are smaller molecules. Although I don't know how BOINC does it, like if it reserves the maximum space per WU or it just cuts the WU if it exceeds the max space.

The latter.

Memory and disk usage will grow while crunching as the task requires until completion, it reaches the limit or reaches the BOINC Mgr disk limit percentage set in preferences.

They work for me. I have downloaded 24 work units (a quota limit), and they take only 1 GB disk space in total. I am running three at a time (4 cores each), and they are taking only about 1 GB memory each.

They run for about 40 to 60 minutes on my i7-8700, which is ideal.

No problems on my computers. Seem to be running ok.

---

Great! Since the last QMML ones were so short that they spammed the conda server I made these 5 times larger (so you calculate up to 50 conformation energies in each WU, in some cases less if I didn't have 50).