Folding Forum

few questions

1. why is it so large
2. what can i delete, reduce, change settings to prevent this from happening again:
I have reduce the size of the WU down to normal, this is supposed to cap at 10G, yet i see the 3 work folders total > 22G. Not acceptable.

Also if this is going to continue to be an issue, is it possible to move fahclient/ out of /var/lib into user space without causing any issues?

Thank you

Actually, your total is shown as 21 GB. What the du utility is showing is the total for the entire directory tree at the bottom, you don't sum up the individual amounts for each subdirectory. So what you do have is 8.8 GB of files in the work directory and 6.4 GB of files in the subdirectory for logs. I expect most of the remaining space is being used by your current log file located in /var/lib/fahclient/. That may be so large if you are getting a large number of error messages or have been running a very long time since your last reboot and restart of the client.

As for the WU size set in the client, that relates to WU upload size after processing, not the working files. But one of the files kept in the work area is a log, that may have blown up for the same reason - large number of error messages.

Right at the moment, no Core_a4 Work Units are being processed. It is possible but not guarantied that no more ever will. Some researcher may discover s/he need some more work to make their paper more robust.

If you delete the /var/lib/fahclient/cores/cores.foldingathome.org/Linux/AMD64/Core_a4.fah directory and it is never used again, you save 6 meg! If it is used again it will be re-created. Not a win. but not a show stopper.

[I am just a user, I have no inside information. If you or any member of you team is caught, I will disavow any knowledge of your operation. This message will not self destruct.]

With those 2 statements, is it also safe to delete the log file to clear up that 6.4G?

Yes.

Log files are sometimes useful in tracking earlier errors but a ceertain number of them are accumulated and then deleted. Restarting the client periodically keeps any one log from getting too big.

Thank you both for the info. Ill keep a better eye on my log files and will restart the client more often.

You've been assigned WUs that use FAHCore_a4 and FAHCore_a7, so those two FAHCore's have been downloaded. If you delete them, they will immediately download again when a WU needs them so there's no point in deleting FAHCore_a7 since those WUs are often being assigned. WUs for the older FAHCore_a4 are either very rare or no longer being assigned so you might as well delete it unless it happens to be currently in use.