Comments on: Notes on how to speed up the trb resync process after data corruption http://ztkfg.com/2020/07/notes-on-how-to-speed-up-the-trb-resync-process-after-data-corruption/ 198.211.113.164 // 6326 273B 61A7 00AF 4CD9 5A7B 8C6C AB19 24A6 4DEC Mon, 13 Apr 2026 17:48:46 +0000 http://polimedia.us hourly 1 By: whaack http://ztkfg.com/2020/07/notes-on-how-to-speed-up-the-trb-resync-process-after-data-corruption/#comment-332 whaack Thu, 23 Jul 2020 14:37:00 +0000 http://ztkfg.com/?p=477#comment-332 Hm you're right, should have kept it. I won't be surprised if I have an opportunity to do this again in the future. Hm you're right, should have kept it. I won't be surprised if I have an opportunity to do this again in the future.

]]> By: Jacob Welsh http://ztkfg.com/2020/07/notes-on-how-to-speed-up-the-trb-resync-process-after-data-corruption/#comment-329 Jacob Welsh Sun, 19 Jul 2020 18:49:06 +0000 http://ztkfg.com/?p=477#comment-329 > Remove your most recent blk000n.dat file, since it should be the file that is corrupted. That's unfortunate - if you'd kept it, we could test the hypothesis since a corrupt block would be gracefully rejected by eatblock. > Remove your most recent blk000n.dat file, since it should be the file that is corrupted.

That's unfortunate - if you'd kept it, we could test the hypothesis since a corrupt block would be gracefully rejected by eatblock.

]]>