Open xinzhongyoumeng opened 3 weeks ago
I find the reason is the in-memory cache was not fully flushed to the underlying database during shutdown.(https://docs.goquorum.consensys.io/reference/logging-and-errors). I don't know the kroma geth client if can do something for this error?
I'm not sure what is causing the error you are getting from pebble db, but it could be database corruption due to an unclean shutdown. If it still happens after rebooting the system and trying again, you may need to delete the database and sync over again.
Issue type
Bug
OS platform and distribution
Ubuntu 22.04
Current behavior?
restart the geth client will panic when use pebble as the backing database. The log is below:
the geth will circular restart.As you can see the ERROR is Dangling trie nodes after full cleanup. What does that mean?
Expected Behavior?
The geth client can restart normally.
Standalone code or description to reproduce the issue
restart the geth client when use pebble.
Additional context
Because the snapshot is use pebble, so we also use the pebble.