so for some reason, i deleted the latest blk03xxx.dat and its related rev.dat file in .bitcoin/blocks/ folder.
Now, when i run the bitcoind command, starts to build up the headers and blocks.
After one entire day, the blocks are at 4xxxxx and headers are at 7xxxxx
i mean, i just deleted one blk.dat and rev.dat file. Supposedly it should be taking so long, right? Why is it taking so long?
Any workaround, please?
i believe its the mismatch of the index which then cant find the corresponding height thus started again from zero
i personally played around with my node to add better rules, features.. and to play around with other things.. so its been awhile since reading cores base code for things like this (it was a nice change to stretch those old brain muscles)
i presumed that it would not be a problem as my node doesnt have that problem, but turns out core does still have that problem
i kinda knew there might have been a re-scan risk but was not sure as it has been a while since looking into that part of the code to remember which was my code vs core base code,
it just seemed such an obvious fix. that i thought the otherday it was just standard base code that allowed easily transfer of partial data.
i was expecting it to just quick scan blk vs rev to then force utxoset into ram and then build new blockheight from peers IBD for the rest(ontop of what you had).
sorry i misled you, but it probably still did save you a bit of time..
it might be worth you making a suggestion to core to change their cludgy code that only operates in "one way or zero" and is not as intuitive as it could be about less than full perfect archiving