-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPFS add -r hang (many files, progress bar disappears) #1408
Comments
@sroerick progress bar disappearing? that's a new one. can you repro it reliably? hang in general sounds related to the "Metadata" problem (i.e. make our Metadata object that addresses symlinks, fifos, etc)). |
I think I may be seeing this as well. I've been noticing it with a build I've been using for about a month, but just the hang symptom, progress bar was still visible. When the daemon is running, it would hang, when I stop the daemon, I can add the whole directory without issue. Today, I've built from master@8668f40915829d78916b94ed9bcfb1ff53fb0cb9 and I see this as described. I'm attempting to add the entire go-ipfs repo at that same commit. With the daemon running, it hangs at
If I kill the daemon and retry, I see it error on one of the next items
Full output and stack trace from command which halted before I SIGQUIT it: https://gist.github.com/rtlong/07c7d7f9c0f4c02f0100 |
@whyrusleeping this is a really bad UX bug. we should fix this asap |
marking as fixed. Reopen if you can reproduce (this may not be entirely caused by the symlink issue, but its likely) |
@davidar ipfs/team-mgmt#29 (comment) The non-symlink part of this issue is a duplicate of #1072 |
To clarify, there are 2 types of bugs here remaining:
|
Using FreeBSD:
I was experimenting with adding a large number of files to IPFS, and found some errors.
Some specific files caused add -r to hang. By hanging, I mean that the progress bar disappeared, there was no indication of what file was presently transferring, and there did not appear to be any disk activity or significant cpu activity.
I don't know that there was any specific quality to the files. I could solve the issue by removing the file, or by adding the file by itself using "ipfs add". Once the file had been hashed on its own, "ipfs add -r" resumed working.
A traceback of the ipfs daemon hanging can be found here: http://sportsteam.link/~roerick/goreport2.txt
More info on IRC here:
https://botbot.me/freenode/ipfs/2015-06-21/?msg=42494305&page=3
The text was updated successfully, but these errors were encountered: