Skip to content
This repository has been archived by the owner. It is now read-only.

Pinning does not happen concurrently but in sequence... #57

matthiasbeyer opened this issue Apr 8, 2017 · 3 comments


None yet
4 participants
Copy link

commented Apr 8, 2017

(Pasting this here because I'm not sure whether it belongs to)

Version information:

go-ipfs version: 0.4.8-
Repo version: 5
System version: amd64/linux
Golang version: go1.8


Bug, unexpected behaviour




If I run cat hashes | while read h; do ipfs pin add "$h" & done or ipfs pin add (so it reads from stdin) and paste a list of hashes into stdin, it seems to try these hashes in sequence rather than concurrently (what would be the expected behaviour).

Because of this I failed to pin ~25 hashes for the last 3 days. Just because the very first hash couldn't be fetched. All others seem to work now...


This comment has been minimized.

Copy link

commented Apr 8, 2017

< hashes | ipfs pin add - might work better.

ipfs pin add works in serial as for pin lock.

@lgierth can we resolve it somehow? We don't need to hold pin lock while fetching.


This comment has been minimized.

Copy link

commented Apr 8, 2017

Workaround for now is a round of ipfs refs -r <hash> (which works concurrently too) and then the pin round.


This comment has been minimized.

Copy link

commented May 23, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.