-reindex flag immediately screws up database #14313

issue ghost opened this issue on September 24, 2018
  1. ghost commented at 9:01 PM on September 24, 2018: none

    After upgrading and reindexing, I goofed up and hit the 'bitcoind -reindex' command again when it was just done reindexing. So, I could wait another full day for it to finish. Perhaps it's an idea to put a safety in, when starting bitcoind or bitcoin-qt with the -reindex flag, that it first asks if you want to reindex.

    If this is too much of a nitwit safety, this issue can be closed.

  2. livestradamus commented at 12:40 PM on September 25, 2018: none

    A confirmation dialogue of (y/N) is perhaps reasonable, considering we're about to index hundreds of GBs. On the flip-side, we should be reading very carefully every command we're about to send.

  3. ghost commented at 2:02 PM on September 25, 2018: none

    Agree, we should take care what commands we use. I've been working with bitcoind for years now, these are errors that slip in when arrowing up a previous command (because you don't want to type out the whole alternate datadir, for instance) Anyway, I'd applaud it, would be quite user friendly.

  4. MarcoFalke commented at 12:25 PM on April 26, 2020: member

    The feature request didn't seem to attract much attention in the past. Also, the issue seems not important enough right now to keep it sitting around idle in the list of open issues.

    Closing due to lack of interest. Pull requests with improvements are always welcome.

  5. MarcoFalke closed this on Apr 26, 2020

  6. DrahtBot locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-17 15:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me