`geth export` tries to write on read-only datadir about go-ethereum HOT 3 CLOSED

Are you sure you stopped the geth gracefully?

The log INFO [03-24|10:33:57.589] Failed to load journal, discard it err="unmatched journal want daeb87735849095c0e81fd38e9ddb5fa48f7b59874c02500d0022b5633d67a59 got e9db26f61c707a6d23b4af55e0d872cc9a58fa871458c5cc2d75badfb88edb13" indicates an unclean shutdown occurred. The extra state histories also relevant with the it.

The behavior is expected. Geth will try to repair the db after unclean shutdown, while geth export rejects all the mutations. Please make sure to always stop node properly. If you are using docker, don't forget to add -t 300 for longer termination period.

from go-ethereum.

Thank you for the answer. I should send SIGTERM to gracefully stop my node like killall geth or killall -TERM geth.

I used to press Ctrl+C sending SIGINT to the node and no problem with the past versions. But it no more gracefully stops my node. When I googled, there were some recommendations to try SIGINT, SIGHUP, or SIGABRT signals, but all of them cannot gracefully stop my node.

from go-ethereum.

Closing this; the combination of "unclean shutdown necessitating cleanup" and "geth export" do not work. In order to fix it, a startup with repair is needed, followed by a clean shutdown.

from go-ethereum.