GC basically useless for now

[suutaku]

go-ipfs version: 0.4.21-rc3-2b41ca17e-dirty
Repo version: 7
System version: amd64/darwin
Golang version: go1.12.5

ipfs daemon --enable-gc

ipfs gc takes too long and StorageGCWatermark looks like not working.
we use ipfs as a file transfer and temp file storage.
first we download files and pin it so other peers can get it immediately.
when process was done. we upload files and pin it. finally, if all process was done, we delete files we downloaded and unpin from ipfs. we cannot run ipfs repo gc because it will make our system frozen. So repo keeping grow until ipfs can not upload or download.
gc Enhancement is in process? or we should find other way to deal with it?

[aschmahmann]

@suutaku Is this a new issue or a regression? Do you get the same behavior with earlier versions of go-ipfs like 0.4.20 or 0.4.19?

Is this issue a duplicate of #6322, or is there something else? Any additional information you can give would be very helpful.

There are existing issues/enhancement requests in place for making GC a non-blocking operation and some thoughts on how this might happen at #4382.

[lsji07]

Is this not a config issue?

This could be as GC is current set to 90% limit on a standard config but the IPFS node is initially limited to 10GB. People know to change the node limit but not the GC limit

I would say that with the standard config the GC would never happen...unless you use your node at capacity alot...

If you want the node to auto garbage collect i would have though you need to set the GC limit lower or to suit your storage requirements.

Edited as put 90GB originally...lol..