-
-
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
Only partially able to read file through ipns mount #5328
Comments
@Stebalien Any thoughts? |
When that happens, could you check This could also be #5183. |
This is what the output of "ipfs swarm peers --streams" looks like when it is stuck mkunal@node-1:~$ ipfs swarm peers --streams |
Damn. Assuming peer A is downloading and peer B is serving, can you run |
On peer B (serving): On peer A (downloading): On peer B (serving), I verified the blocks exist by printing the raw data using "ipfs object get QmSw6qxguQ3ZSk8ufA416pVvVHwSotKppQg54VUHEoGrrv" |
Interesting... Does peer B have those blocks? Does it hang when running |
No hanging on peer B. $ipfs block stat QmXFRdKuZiCcnRiTNyEcKtwL127WDjYrnu4C5pScykR5hg $ ipfs block stat QmSw6qxguQ3ZSk8ufA416pVvVHwSotKppQg54VUHEoGrrv $ ipfs block stat QmXC8zjajA5q3RRJa9oXJxkVBN5ibihjnJvPZRayMERCjC On peer A (downloading), it hangs for the above 3 commands. |
Here are the results: EDIT: added the binary |
Can I get the exact binary you used as well? |
My apologies. Added the binary in the tar. |
Which peer is this and would you mind doing the other peer as well? |
Edit: the two files were swapped Sender (peer B): Downloader (peer A): |
Awesome! Thanks! One more question. Is this the first time you've started these nodes (trying to reproduce). |
I am renting these machines from Cloudlab (https://www.cloudlab.us/). Since the time I obtained them (about 8 days ago), they have been running. I didn't reboot them. Does that answer the question? |
Please let me know how I can help to identify or fix the issue. |
Not sure if this helps though I would like to point out that using "ipfs get file.txt" works as it should. It downloads the file in its entirety without any issues. |
Oh. Hm. That's really odd. Can you run on Just to make sure |
Yes, file.txt is the file trying to be downloaded. In the output, it prints one line and then hangs. Ah, I think I see what you mean. In the earlier experiment, which worked: In the /ipns mount scenario, which is hanging: |
Wait, but |
I just tried that and it succeeds. on peer A (the client trying to download): |
Does it actually download the complete file (trying to rule out a bug in |
And thank you for all your help on this! |
Sure thing. Happy to help! Please feel free to let me know any way I can help. I did "cat file.txt" and it printed the entire file. |
So, to summarize, on peer A:
|
Yes. |
No but the |
If you re-run these commands (#5328 (comment)), do you get the same results? |
No, it varies. Sometimes more entries, sometimes less. |
What's the output of |
(on both machines) |
I ran "cat /ipns/Qm.../file.txt". After it hangs, obtained the output of "ipfs diag cmds". Peer A (downloader): Peer B (sender): |
And does Internally, it looks like anything that might cause |
ipfs get /ipns/Qm.../file.txt works
ipfs refs /ipns/Qm.../file.txt works
cat /ipns/Qm.../file.txt hangs
After its hanging, get the list of hashes using "ipfs bitswap want list"
For any one of the hashes from the list (let's say Qmhash), "ipfs refs
Qmhash" prints couple lines of hashes and then hangs.
On Aug 24, 2018, at 6:45 PM, Steven Allen <notifications@github.com> wrote:
And does ipfs get *still work*? Does ipfs refs *still hang*?
Internally, it looks like anything that might cause ipfs refs to hang
should cause ipfs get to hang.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5328 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AToQMDc04Sts6zmseQgcR7QmRwWHFGRCks5uUIIXgaJpZM4Vq3V->
.
|
One more data point :
cat /ipns/Qm.../file.txt hangs
But, if I run ipfs refs /ipns/Qm.../file.txt (which works) and then "cat
/ipns/Qm.../file.txt" (this succeeds)
On Aug 24, 2018, at 6:45 PM, Steven Allen <notifications@github.com> wrote:
And does ipfs get *still work*? Does ipfs refs *still hang*?
Internally, it looks like anything that might cause ipfs refs to hang
should cause ipfs get to hang.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5328 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AToQMDc04Sts6zmseQgcR7QmRwWHFGRCks5uUIIXgaJpZM4Vq3V->
.
|
Version information:
go-ipfs version: 0.4.18-dev-4bca53e
Repo version: 7
System version: amd64/linux
Golang version: go1.10
Type:
Bug
Description:
I created a text file (size 300MB) with random ascii characters using the following command:
base64 /dev/urandom | head -c 300000000 > file.txt
Added this text file to /ipns mount on the machine
On another machine, I tried reading a third of the file using head:
head -c 1000000 /ipns/QmezBPmm4RRBRTBYPhVHsSSAPS2Q8hRTDd3PrfTsG8yvnf/file.txt
This command prints some number of lines and then gets stuck permanently.
Using debugging log, the following line is repeated "10:42:23.157 DEBUG bitswap: 9 keys in bitswap wantlist workers.go:185"
The text was updated successfully, but these errors were encountered: