Whats the clue ?

Nothing But Idle Time
Nothing But Idl...
Joined: 24 Aug 05
Posts: 158
Credit: 289,204
RAC: 0

This is a very old topic. If

This is a very old topic. If you have the desire and the time you can review this thread No Disk Space. I don't remember what is in it so I don't promise that there is anything concrete that you can use. --NBIT

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,852
Credit: 111,034,400,046
RAC: 34,808,744

RE: This is a very old

Message 38420 in response to message 38419

Quote:
This is a very old topic. If you have the desire and the time you can review this thread No Disk Space. I don't remember what is in it so I don't promise that there is anything concrete that you can use. --NBIT

Yes, that thread contains a lot of discussion about the possible causes of messages about lack of disk space. By all means, people can go through it if they wish but please realise that there was a lot of conjecture until Walt Gribben came along and pointed out some things in the code. I made a number of posts about what I thought might be happening, much of which was wrong because only someone able to fully read and understand the code would know the key points. Walt was such a person and you can read his full explanation here.

The following is a selected quote from Walt's post which contains the information to explain the current problem that Carlos was having. Carlos solved it with a bigger partition :). I've put some further explanation into Walt's quote, hopefully to make things clearer and easier to understand. My comments are in green.

Quote:
Also note that "leave at least __GB free" can't be smaller than .001 (1,000,000 bytes), if you set something smaller the scheduler uses .001 instead of your preference. That leaves some slack for administrative files (client_state, scheduler requests/replies, std*.txt, stuff like that)

Carlos had set this to zero so he got 1,000,000 bytes anyway.

Quote:

Older BOINC clients don't send the space BOINC uses, so it only makes one calculation:

"host free disk space" minus "leave at least __GB free"

Thats it for determining how much it can use.

Once the "available space" is calculated, it makes sure there's enough space for the workunit.

While its building a list of workunits to send, the scheduler keeps track of the disk space needed by the workunit. It counts:

space needed for each file not already on the host

space needed to run the workunit (100MB or 100,000,000 bytes)

BOINC makes sure there is 100MB of free space for creation of temporary files on top of whatever space is actually needed to store the downloads before it will allow you to get more work.

Quote:
So the minimum space needed is 101 megabytes (101,000,000 bytes) plus the space needed for any files it has to sent. At least for Einstein@Home, other projects have other requirements.

Please note carefully that last bit about "space needed to run the workunit" - ie 100MB. This means that a preference to leave 0MB free actually causes BOINC to need to have 101MB free. Carlos only had 60.4MB free until he set up the new partition.

Hope this might help explain some of the recent spate of "Not enough disk space" errors that have been occurring.

Cheers,

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.