Seadrive not clearing my cache folder. The cache has approximatly 200 GB of files. I tried different cache size limits but nothing helped.
In case this matters, it took more than a couple of weeks for this cache to be synced with the server. This was a problem by itself but I’m not sure if it is related to clearing the cache. In case it matters, the sync took that long despite the client being connected to the server on a gigabit network.
I see this in the log without any files removed:
[09/09/19 21:50:01] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:50:01] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:50:01] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:51:01] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:51:01] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:51:01] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:51:01] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:52:01] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:52:01] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:52:01] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:52:01] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:53:02] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:53:02] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:53:02] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:53:02] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:54:02] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:54:02] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:54:02] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:54:02] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:55:02] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:55:02] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:55:02] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:55:02] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:56:03] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:56:03] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:56:03] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:56:03] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:57:03] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:57:03] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:57:03] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:57:03] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:58:03] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:58:03] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:58:04] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:58:04] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 21:59:04] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 21:59:04] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 21:59:04] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 21:59:04] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/09/19 22:00:04] file-cache-mgr.c(2590): Cleaning cache space.
[09/09/19 22:00:04] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
[09/09/19 22:00:04] file-cache-mgr.c(2613): Cache cleaning done.
[09/09/19 22:00:04] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
You may have a look at the cache folder. Are the files in the cache all (or mostly) already uploaded to the server? If the files are not uploaded yet, they won’t be removed from cache.
Another way to debug this issue is to set the environment variable ‘SEADRIVE_DEBUG’ to ‘sync’. Then restart seadrive. There should be more debug message on why any file in the cache is not removed. You should set the env variable in Windows system property. And make sure you’re running the latest version of SeaDrive.
Hello,
I had the same problem with the Seadrive 1.0.7 Client
I wanted to send 300GB of data by copying and pasting it to the Seadrive drive.
(files of about 2GB each)
The computer in question had 60 GB left on the hard disk.
Very quickly the hard disk was overloaded, more space on the computer.
1- The Seadrive Client should regularly check the available space on the hard disk.
2- The Seadrive Client has a 10GB cache, why do I have a file-cache folder with 60GB of data inside ?
On my side it was sent 26GB on the server in all
that being said, this new version seems to work much better.
Congratulations for your efforts
Jonathan, thanks for the tips! I turned on debug logging and below is more information.
The Seadrive tray icon is green and not uploading anything.
Here is a log of the client startup
[09/11/19 13:35:32] seadrive.c(684): Starting SeaDrive client 1.0.7
[09/11/19 13:35:32] seadrive.c(686): SeaDrive client source code version 97c05e657e326b717014336beefdce1c6003e9dc
[09/11/19 13:35:32] seadrive.c(709): rpc server started.
[09/11/19 13:35:32] seadrive.c(724): Limit access to current user session only.
[09/11/19 13:35:32] seadrive.c(729): Mount virtual drive as removable disk.
[09/11/19 13:35:34] start to serve on pipe client
[09/11/19 13:35:35] start to serve on pipe client
[09/11/19 13:35:37] start to serve on pipe client
[09/11/19 13:35:37] start to serve on pipe client
[09/11/19 13:35:38] repo-mgr.c(2549): switching account to ****.
[09/11/19 13:35:40] sync-mgr.c(1433): All repo fs trees are loaded.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘PhonePhotos’ sync state transition from ‘synchronized’ to ‘committing’.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘Backups’ sync state transition from ‘synchronized’ to ‘committing’.
[09/11/19 13:35:40] sync-mgr.c(2612): All operations of repo PhonePhotos(ce8f6631) have been processed.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘_Main’ sync state transition from ‘synchronized’ to ‘committing’.
[09/11/19 13:35:40] sync-mgr.c(2612): All operations of repo Backups(2be12be2) have been processed.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘_Work’ sync state transition from ‘synchronized’ to ‘committing’.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘Backups’ sync state transition from ‘committing’ to ‘synchronized’.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘PhonePhotos’ sync state transition from ‘committing’ to ‘synchronized’.
[09/11/19 13:35:40] sync-mgr.c(2612): All operations of repo _Main(685018be) have been processed.
[09/11/19 13:35:40] sync-mgr.c(2612): All operations of repo _Work(8f022489) have been processed.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘_Main’ sync state transition from ‘committing’ to ‘synchronized’.
[09/11/19 13:35:40] sync-mgr.c(580): Repo ‘_Work’ sync state transition from ‘committing’ to ‘synchronized’.
[09/11/19 13:36:33] file-cache-mgr.c(2590): Cleaning cache space.
[09/11/19 13:36:33] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
Then I see a set of lines like the following. All these files are actually uploaded and on the server.
[09/11/19 13:36:33] file-cache(2564): [cache clean] Skip file 2be12be2-70f0-4cb2-b30c-49a21610a27c/gopro/2019.07.20/1/100GOPRO/GH040265.MP4 since it is not uploaded.
[09/11/19 13:36:33] file-cache(2564): [cache clean] Skip file 2be12be2-70f0-4cb2-b30c-49a21610a27c/gopro/2019.07.20/1/100GOPRO/GH030265.THM since it is not uploaded.
[09/11/19 13:36:33] file-cache(2564): [cache clean] Skip file 2be12be2-70f0-4cb2-b30c-49a21610a27c/gopro/2019.07.20/1/100GOPRO/GH050265.MP4 since it is not uploaded.
[09/11/19 13:36:33] file-cache(2564): [cache clean] Skip file 2be12be2-70f0-4cb2-b30c-49a21610a27c/gopro/2019.07.20/1/100GOPRO/GH040265.THM since it is not uploaded.
Then I see a set of lines like the following. These files are also uploaded and already on the server. I removed some of the path on the first line and the other lines are similar, i.e. they are all under the _MACOXS directory. This is on a Windows machine.
685018be-4694-4ec8-86b7-2238d823627c/Dropbox/Documents////__MACOSX//._Chase .pdf
[09/11/19 13:36:33] file-cache(2513): [cache clean] Skip file 685018be-4694-4ec8-86b7-2238d823627c/* since it is ignored on commit.
[09/11/19 13:36:33] file-cache(2513): [cache clean] Skip file 685018be-4694-4ec8-86b7-2238d823627c/*** since it is ignored on commit.
Then the following lines:
[09/11/19 13:36:33] file-cache-mgr.c(2613): Cache cleaning done.
[09/11/19 13:36:33] file-cache-mgr.c(2615): Removed 0 files, cleaned up 0 MB
[09/11/19 13:37:33] file-cache-mgr.c(2590): Cleaning cache space.
[09/11/19 13:37:33] file-cache-mgr.c(2592): 337 files in cache, total size is 212394 MB
The upload of these files took a very long time (probably 2 weeks) and he laptop was on and off during that time and it might have crashed once for some unrelated reason, can’t remember for sure. The upload finished about 3 days ago. I was hoping that the cache will be cleared when the upload was finished but the files are still taking too much space. My cache limit is 10GB