I've noticed that while the client automatically deletes the input zip's (eg 77in0.zip ) it leaves the output zip's (eg in0__blender_session0000000077_range0000000019_0_frame0000000006_3_0.zip)

Is this intentional? Will the client start deleting them when it runs low on disk space?

> Is this intentional? Will the client start deleting them when it runs low on
> disk space?

If the server makes a major crash and a lot of the results are deleted a partial recovery can be made from the files left on the clientside (by users manually re-uploading the results).
Theoretically the files will be deleted automatically when the client is close to the diskspace limits set by the user, but please confirm this. My guess is that the cleanup process is run just after contacting the server for more work.

Hi,

I have 6 old WU input files (like 125in0.zip or 117in0.zip, etc) in the project folder. I think that BOINC must delete old files but it didn't.

All other projects deletes their WU input files correctly after finishing crunch.
Is there a problem in my BOINC client or in BURP project?


I have BOINC CC 4.72.
Projects: BURP, LHC, CPDN, E@H, P@H, S@H, S@H beta, SZDG

Computer:
P4-2.6 GHz HT, RAM 1Gb
ATI Radeon 9600 PRO Series Videocard
OS: WinXP SP2 Pro

---

Hi,

I have 6 old WU input files (like 125in0.zip or 117in0.zip, etc) in the project folder. I think that BOINC must delete old files but it didn't.

All other projects deletes their WU input files correctly after finishing crunch.
Is there a problem in my BOINC client or in BURP project?


I have BOINC CC 4.72.
Projects: BURP, LHC, CPDN, E@H, P@H, S@H, S@H beta, SZDG

Computer:
P4-2.6 GHz HT, RAM 1Gb
ATI Radeon 9600 PRO Series Videocard
OS: WinXP SP2 Pro

If one of the files is in use the directory will not be cleaned up correctly. BURP leaves blender.exe running under some circumstances (it can be running for weeks after processing is supposed to be complete).h

---

BOINC WIKI

Hi,

I have 6 old WU input files (like 125in0.zip or 117in0.zip, etc) in the project folder. I think that BOINC must delete old files but it didn't.

All other projects deletes their WU input files correctly after finishing crunch.
Is there a problem in my BOINC client or in BURP project?


I have BOINC CC 4.72.
Projects: BURP, LHC, CPDN, E@H, P@H, S@H, S@H beta, SZDG

Computer:
P4-2.6 GHz HT, RAM 1Gb
ATI Radeon 9600 PRO Series Videocard
OS: WinXP SP2 Pro

If one of the files is in use the directory will not be cleaned up correctly. BURP leaves blender.exe running under some circumstances (it can be running for weeks after processing is supposed to be complete).

Thank you, it seems you're right.

Another WU that is new has a download error (by timeout) and was deleted 15 min ago. But shouldn't BOINC continue download it after some errors during downloading process?
Or it's a new bug in BOINC CC 4.72?

---

...
I think that BOINC must delete old files but it didn't.

All other projects deletes their WU input files correctly after finishing crunch.
Is there a problem in my BOINC client or in BURP project?

I have BOINC CC 4.72.
Projects: BURP, LHC, CPDN, E@H, P@H, S@H, S@H beta, SZDG
...

If you run CPDN you will have noticed it leaves the workunits after completion in the projects folder until BOINC has to free up hdd space du to memory limits you set in your general preferences.
And thse models are much bigger than a simple blender file.

Despite of this, I like to have the blender input files on my pc.
When I have some time, I like to open these files in blender and have a look around how someone did something...
My way to learn a bit of blender.

Andy

---

BURP uses the same strategy as CPDN for files. The files are stored on your computer between each workunit so that you won't have to download them again the next time you get a workunit belonging to the same session.
After a session has completed the file will stay there untill BOINC eventually cleans it up (or untill I figure out how to send the cleaning messages from the serverside automatically upen session completion, this is late beta stuff though).

If you should signalize a deletion to all clients it would be nice to make the original Blender files available for download in the session gallery. Maybe some people could be interested in examining the source files they rendered. ;)

---

Good idea, noted.

BURP uses the same strategy as CPDN for files. The files are stored on your computer between each workunit so that you won't have to download them again the next time you get a workunit belonging to the same session.
After a session has completed the file will stay there untill BOINC eventually cleans it up (or untill I figure out how to send the cleaning messages from the serverside automatically upen session completion, this is late beta stuff though).

Well, I understood about files.
Some strategy also is used by Einstein@home. And they know how to delete unnecessary WU files. You can ask them about this mechanism.

---

Well, I understood about files.
Some strategy also is used by Einstein@home. And they know how to delete unnecessary WU files. You can ask them about this mechanism.

BOINC-wiki, always usefull source of information :)

---

PrimeGrid
Administrator