Adding files fails if not enough space on primary drive
See original GitHub issueI use ipfs-desktop 0.8.0.0 (and go-ipfs 0.4.21) on Windows 10. I configured IPFS to use a secondary partition for the blocks (drive N in my case). IPFS is installed on my primary drive, C. I created this configuration by editing the config.json
of IPFS Desktop and its ipfsConfig / path
value.
I tried to add a bigger file (3.3 GB). IPFS first tried to create multiple files in the %APPDATA%/IPFS Desktop/blob_storage
. I didn’t expect this, because I set the storage path to the drive N.
When I didn’t have enough space on my drive C for those files, the adding failed with a general error message, but I didn’t get an exact error explaining the reason.
It would be good to check the space on both the primary drive (with the blob_storage folder, C in my case) and the drive containing the blocks (N in my case) if they have enough space for the adding before starting the operation, and let the user know if they need to make more space to continue.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (5 by maintainers)
Top GitHub Comments
That’s great! Although, I will leave this issue open until I can find a way to make sure this doesn’t happen.
No, unfortunately no. We’re using
js-ipfs-http-client
which then makes requests to the IPFS HTTP API. The paths of the API could be easily mapped to strict commands, however that’s not a current feature of ours.When you use CLI, the
ipfs add
pins added data, so it is protected against GC. You can remove pins viaipfs pin rm $CID
, or disable automatic pinning by executingipfs add --pin=false
ps. adding big files should be MUCH faster in v0.13.2