When I run “seaf-fsck -r,” the check still checks two Libraries/Repos that I have deleted. These repos do not show up in the UI, not even the trash. Per the manual, I tried running:
cd <install-path>/seafile-server-latest
./seahub.sh python-env python3 seahub/manage.py clear_invalid_repo_data
However, the libraries still show up when I run the fsck. Interesting, they do not show up when I run a GC. I also ran a GC with the -r option but it did not have any affect.
In RepoInfo, “634c7c6c-1cdf-432d-9258-eb82cb480e80” and “3adb32ea-7c3a-4a9d-abf6-1bad15035ab2” have the same name, but it is one of the repos that should have been deleted.
Does these repo id exist in VirtualRepo table? If so, it means they’re “virtual libraries” created for shared folders. It’s normal that fsck still checks them.
Thanks @Jonathan, yes two of he three show up in VirtualRepos, however I am not sharing either via any shared folders. Is it possible that I had them synced to other devices and did not properly remove them from those devices? Would deleting said devices from “Linked Devices” help? How can I see what within my environment is still “using” them and remove them.
Virtual libraries are also be created when you sync a folder within a library. Currently virtual libraries are removed when you remove the parent library. Unsharing or unsyncing the folder cannot remove the virtual library.
It is unfortunate that I cannot delete these virtual libraries that are no longer in use by any client. How can I tell how much space they are using and potentially delete some of that data?
I have another repo that is a virtual library, but shows up twice (by name) in the RepoInfo table with a different repo_id. What could this be and how can I get rid of it?