Closed rmulhol closed 4 years ago
It looks like there's a syscall trying to create a file, which has blocked other readers for 5407
minutes, that is, 90 hours or almost four days. This is odd -- are you using some particular filesystem? As in, is this a normal unix environment, or is there some non-standard filesystem used for the data directory?
Thanks for the insight! Yes, using ZFS (running on OS X) to manage external drives.
@holiman can we get some pointers for debugging this issue? It may be an issues with the osx implementation of ZFS, while running a node on Linux I don't think I ran into this issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi there,
please note that this is an issue tracker reserved for bug reports and feature requests.
For general questions please use the gitter channel or the Ethereum stack exchange at https://ethereum.stackexchange.com.
System information
Geth version:
geth version
1/8/13-stable OS & Version: Windows/Linux/OSX OSX Commit hash : (ifdevelop
) 225171a4bfcc16bd12a1906b1e0d43d0b18c353bExpected behaviour
Geth would continue to sync to the head of the chain and continue running.
Actual behaviour
Geth stops syncing new blocks. Needs a force quit and restart.
Steps to reproduce the behaviour
Not sure how to reproduce, not sure why this would happen in the first place. The stack trace below shows the node syncing regularly until block 6368257, doing ~3 blocks ever ~19 seconds. Then, there is no further activity for ~18 hours, at which point I attempt a force quit. This continues for ~3 days, until I quit via
LoudPanic
(repeated force quit).Backtrace