old workunits
17 Jun 2008 8:48:25 UTC
Topic 193726
(moderation:
I've just moved some old workunits and associated files to a temporary directory:
total 48788
-rw-r--r-- 1 boinc nobody 139 May 11 2007 config_S5R1a.cfg
-rw-r--r-- 1 boinc nobody 139 May 11 2007 config_S5RIa.cfg
-rw-r--r-- 1 boinc nobody 2745667 May 11 2007 earth_05_09
-rw-r--r-- 1 boinc nobody 3539016 May 11 2007 h1_0373.75_S5R2
-rw-r--r-- 1 boinc nobody 3539016 May 11 2007 h1_0373.80_S5R2
-rw-r--r-- 1 boinc nobody 3539016 May 11 2007 h1_0373.85_S5R2
-rw-r--r-- 1 boinc nobody 3539016 May 11 2007 h1_0373.90_S5R2
-rw-r--r-- 1 boinc nobody 3234816 May 11 2007 l1_0373.75_S5R2
-rw-r--r-- 1 boinc nobody 3234816 May 11 2007 l1_0373.80_S5R2
-rw-r--r-- 1 boinc nobody 3234816 May 11 2007 l1_0373.85_S5R2
-rw-r--r-- 1 boinc nobody 3234816 May 11 2007 l1_0373.90_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 6 2007 l1_0400.35_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 6 2007 l1_0400.40_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 6 2007 l1_0400.45_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 6 2007 l1_0400.50_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 14 2007 l1_0400.55_S5R2
-rw-r--r-- 1 boinc nobody 3234816 Jun 15 2007 l1_0400.60_S5R2
-rw-r--r-- 1 boinc nobody 274843 May 11 2007 sun_05_09
The client is still running fine. I think these files were supposed to be deleted but that deleting them somehow failed?
old workunits
)
You will have trouble with these two - they are required. I imagine you don't see an immediate effect as the processing takes place in a slots directory and I believe that copies are placed there at the start of crunching of a task. The next time a task starts will probably be the trigger point for problems to occur. I think that tasks will probably be trashed until new copies of the missing files can be downloaded. I'm not sure how "forgiving" the system is about this.
I don't think that will last for long :-).
This is a quick reply to warn you to put the above two back ASAP before the fact they are missing is noticed. I'll edit to supply more info.
MORE INFORMATION
================
The files that BOINC considers to be required are listed in client_state.xml and it is very unwise to delete things without going through that file with a text editor to see what is listed there. The config* files will not be listed so it is OK to delete them but I suspect everything else is likely to be listed and therefore considered to be required.
At best, the deletion of a listed file will issue a warning message of some sort followed by the downloading of those files from the server. At worst, you could easily trash the contents of your cache of work. Please note that the h1_* and l1_* files are NOT tasks but rather the data files on which multiple tasks depend. Deletion of those files could easily trash all the tasks in your cache. The ones you listed are for lower frequencies that were probably completed many months ago so these should not cause problems with current work. However if they are still listed in your state file they will simply be downloaded again, wasting bandwidth.
There was a bug some considerable time ago at the time when the data frequencies you listed were current. At that time, the h1_* files were being deleted but the l1_* files were being overlooked. That's not the entire answer in your case as you still have some h1_* files. If you are really satisfied that these remnant files are really no longer required and they are not listed in the state file then by all means go ahead and delete them. If they are still listed in the state file, you could use the following steps to safely deal with them, if you are really sure you know what you are doing.
* Open the state file in a text editor
* Locate the .... tags that define the h1_* or l1_* file you wish to delete. There will be quite a few lines of info, including download URLs, between the two tags. You will need
very carefully to delete the complete block, including the opening and closing tags.
* Repeat this step for each one of these data files that you are absolutely sure is no longer required.
* If you get it wrong, the consequences are entirely yours as this procedure is not something you would normally need to do.
* When finished, save the state file and exit the editor.
* Restart BOINC (keeping your fingers crossed, hoping you didn't make any editing mistake).
I cannot stress strongly enough that this is not a routine procedure and you could easily trash everything if not careful.
Cheers,
Gary.
RE: RE: -rw-r--r-- 1
)
I just noticed they are referenced from ~boinc/slots/*/sun and ~boinc/slots/*/earth . I think that as long as the task stays in memory the client won't crash.
Done.