user127364: I made files re-accessible. Now we could return to a later, already synchronized state with the files. I tried to put ./bitcoind -reindex-chainstate=0, also in a bitcoin.conf, also directly calling the conf. It goes on reindexing the chainstate.

user208: -reindex-chainstate is an instant operation: it wipes a the chainstate (UTXO) database. It is performed at startup whenever the -reindex-chainstate command-line option, or the reindex-chainstate=1 config file parameter is provided. It cannot be interrupted, but it is so fast this is rarely a concern. It's equivalent to emptying the chainstate/ directory by hand, FWIW.
Whenever the chainstate is behind the blockchain (i.e., you have blocks in your blocks/ directory which haven't been processed yet), the missing blocks will automatically be processed. This will typically happen after a -reindex or -reindex-chainstate, but it can happen outside of those too. E.g. when you wipe the chainstate/ directory yourself, or maybe if restore it to an older backup without making the equivalent restoration of the blocks/ directory.
The naming of these options is somewhat confusing, because what they trigger isn't the actual reindexing, but just the wiping that preceeds it; the reindex is automatic, and progressive (it will continue where it left off if you shutdown and start again, unless you specify the reindex option again at startup; in that case, it is wiped again and you'll start over again).
FWIW, any option, including these, can be disabled using the "no" variant (-noreindex-chainstate here) or passing 0 (-reindex-chainstate=0). But, as explained, that just disables the wiping; it cannot undo a wipe, and thus cannot "abort" the reindexing, as Bitcoin Core cannot proceed without first processing all the blocks it has.

127364: <p>I made files re-accessible. Now we could return to a later, already synchronized state with the files. I tried to put <code>./bitcoind -reindex-chainstate=0</code>, also in a bitcoin.conf, also directly calling the conf. It goes on reindexing the chainstate.</p>
 208: <p><code>-reindex-chainstate</code> is an instant operation: it wipes a the chainstate (UTXO) database. It is performed at startup whenever the <code>-reindex-chainstate</code> command-line option, or the <code>reindex-chainstate=1</code> config file parameter is provided. It cannot be interrupted, but it is so fast this is rarely a concern. It's equivalent to emptying the <code>chainstate/</code> directory by hand, FWIW.</p>
<p>Whenever the chainstate is behind the blockchain (i.e., you have blocks in your <code>blocks/</code> directory which haven't been processed yet), the missing blocks will automatically be processed. This will typically happen after a <code>-reindex</code> or <code>-reindex-chainstate</code>, but it can happen outside of those too. E.g. when you wipe the <code>chainstate/</code> directory yourself, or maybe if restore it to an older backup without making the equivalent restoration of the <code>blocks/</code> directory.</p>
<p>The naming of these options is somewhat confusing, because what they trigger isn't the actual reindexing, but just the wiping that preceeds it; the reindex is automatic, and progressive (it will continue where it left off if you shutdown and start again, unless you specify the reindex option again at startup; in that case, it is wiped again and you'll start over again).</p>
<p>FWIW, any option, including these, can be disabled using the &quot;no&quot; variant (<code>-noreindex-chainstate</code> here) or passing 0 (<code>-reindex-chainstate=0</code>). But, as explained, that just disables the wiping; it cannot undo a wipe, and thus cannot &quot;abort&quot; the reindexing, as Bitcoin Core cannot proceed without first processing all the blocks it has.</p>
