Hi
it may be necessary to delete unused blocks.
this will delete the files that were deleted
remember to shut down your server if you do not use the pro version
my data being in the seafile-data, and the seafile’s data in seafile-client; I know I didn’t make a good use of my brain when I choose those names.
ii libseafile0 6.2.4 amd64 Shared libraries for Seafile
ii libsearpc1 3.1.0 amd64 SeaRPC library for Seafile client
ii python-searpc 3.1.0 all simple and easy-to-use C language RPC framework
ii seafile-cli 6.2.4 amd64 Seafile command line interface.
ii seafile-daemon 6.2.4 amd64 Seafile daemon
Sorry, but I don’t understand the question: I’m on the client side and I’m talking about the internal data space storage used by the seafile client that is too big.
@lemmel I have exactly the same problem. My library is 2.8 TB in size and I try so sync it now with the seafile-cli client. The seafile-data storage is already 300 GB in size and growing. I have no idea whats wrong and why its doing it. I would really appreciate a suggestion from the community.
For me it is either a bug or a feature: so I’m expecting no real answer.
I tried to open a ticket (seafile-client github), but it was close because it was “unlikely a bug”.
So I’m waiting enough time to reopen the ticket.
It must be a bug. I’ve synced 800 GB of 2.8 TB so far and my seafile-data directory is 450 GB in size. That’s ridiculous.
Overall my experience is that seafile is real mess when you try to manage more than 1 TB of data. It’s awful implemented. E.g. the verbosity is so bad, you never know what the application is currently doing.
I’m on seafile for years already, but with smaller data amount. Now my seafile data directory on the server is 10 TB big. Seafile can’t handle such amounts efficiently.
My observation is this: Seafile is downloading the data to the local storage in seafile-data which can grow very big (more than half the size of the actuall library it was in my case), then after a while seafile stops the download and starts to extract the data into its actual destination. So make sure the drive where seafile-data is on, is big enough to handle huge libraries.
Is there a solution to this issue yet. in my case the seafile-data/blocks size was larger than the library’s one. I’m using seaf-cli 8 on ubuntu 20.04. i’m garbage collecting my server every week. so the blocks should not be that large anyway.