Hi Phil, in order to help you, could you please post the opening lines from your Messages tab - so that we can a) see what your set-up is, and b), see the actual error message that's being reported. From that, we'll have something to work on.

Hold up!

Remember that each project has a required minimum disk space. The actual disk space used is normally only a fraction of this required space. So check which projects you are running, check their requirements at https://secure.worldcommunitygrid.org/help/viewTopic.do?shortName=minimumreq (2 GB for CEP2) and make sure you have enough disk space for 4 of them.


Lawrence

It's the messages, the messages, the messages we wish to see, always, and not snippets, but the full works from start to well after the problem appears to occur [Plz let supporters be the judge of what's relevant!]

In the case of disk-space allocation, it's a bit complicated, because... there's this percent to be left free too. If for instance you permit 2GB, and 1.2GB is already used, then if calling for CEP2, it will tell you "0.8GB available, need 1.2GB more". Then, if a percent is set to leave untouched by BOINC, say 50%, and there is only a total of 3GB free space on the data dir partition, BOINC really on outset is going to be using a maximum of 1.5GB. What's net allowed to be used is printed too in the message/event log.

There's more of this stuff, to include a data_dir that's shared with other programs/data [The data dir really should be exclusive to BOINC]. The client will assume everything including what's in the sub-structure to be project related and suddenly there's no space at all [per BOINC logic], even if a disk has 100GB free.

edit: Of course if we have not written a Help / Start Here FAQ for a topic, it's because someone else somewhere else in the usual places has done so already... duplication of effort I so much dislike:

The Local Prefs Wiki [In principle all except 1 or 2 are mirrored off from the website device profile options]: http://boinc.berkeley.edu/wiki/Local_preferences
The more technical/in depth explanation: http://boinc.berkeley.edu/trac/wiki/DiskManagement

NB, some of the maxima have long been upped [practically no restriction, but the size of the field]. For unknown reason some old limits have been left to persist in the wikis... guess is because different versions of client allow different number of digits in a field.