If we are crunching S5R3 should there still be S5R2 "sticky" files (as BM calles them) in my project directory. Is there still some data to crunch for S5R2? Just curious.
If we are crunching S5R3 should there still be S5R2 "sticky" files (as BM calles them) in my project directory.
About a year or so ago, there was a bug in the deletion of used up data files. It was at the time that low frequencies were being crunched (100 - 400Hz) and only the h1_0xxx.xx... data files were being deleted and the l1_0xxx.xx... data files were being left on the participants hard drive.
They really are no longer needed and are only left behind because of the bug which was fixed after I reported it. Consequently, more recent used up data files are properly being deleted when they are finished with. The problem with the old files is that they are still recorded in your state file (client_state.xml) so that if you delete them manually, the server will notice and will simply replace them by sending them afresh. I had many machines in this predicament and here's what I did (I should add that the old files do no harm other than consume space)
* On each affected machine, stop BOINC.
* edit client_state.xml to remove each ..... block that refers to these old l1_0xxx.xx.... data files. Each block contains about 16 lines and care is required to only delete the correct blocks.
* save the edited state file and restart BOINC
* with BOINC running again, go into the E@H project sub-directory and delete the actual data files corresponding with what you removed from the state file.
Of course there are risks (human error) associated with doing this so the responsibility is entirely with the person choosing to do this. If you are not worried about disk space there is really no need to delete the files.
They really are no longer needed and are only left behind because of the bug which was fixed after I reported it. ..... The problem with the old files is that they are still recorded in your state file (client_state.xml)
Thanks! I had noticed they were still in the client_state.xml but just wanted to be sure they were no longer needed before I zapped them in the directory and the xml file. Doesn't really bother me space wise ... just like to clean up every once in awhile ... (oops the dishes are laughing at me) .. so next time BOINC decides E@H needs a rest ...
Just a ?, S5R2 "sticky" files still in project directory
)
About a year or so ago, there was a bug in the deletion of used up data files. It was at the time that low frequencies were being crunched (100 - 400Hz) and only the h1_0xxx.xx... data files were being deleted and the l1_0xxx.xx... data files were being left on the participants hard drive.
They really are no longer needed and are only left behind because of the bug which was fixed after I reported it. Consequently, more recent used up data files are properly being deleted when they are finished with. The problem with the old files is that they are still recorded in your state file (client_state.xml) so that if you delete them manually, the server will notice and will simply replace them by sending them afresh. I had many machines in this predicament and here's what I did (I should add that the old files do no harm other than consume space)
* edit client_state.xml to remove each ..... block that refers to these old l1_0xxx.xx.... data files. Each block contains about 16 lines and care is required to only delete the correct blocks.
* save the edited state file and restart BOINC
* with BOINC running again, go into the E@H project sub-directory and delete the actual data files corresponding with what you removed from the state file.
Of course there are risks (human error) associated with doing this so the responsibility is entirely with the person choosing to do this. If you are not worried about disk space there is really no need to delete the files.
Cheers,
Gary.
RE: They really are no
)
Thanks! I had noticed they were still in the client_state.xml but just wanted to be sure they were no longer needed before I zapped them in the directory and the xml file. Doesn't really bother me space wise ... just like to clean up every once in awhile ... (oops the dishes are laughing at me) .. so next time BOINC decides E@H needs a rest ...
Kind Regards