Can I stop it from re-downloading headers?
Posted: Wed Aug 17, 2011 8:40 pmI upgraded to version 6 (Excellent upgrade in my opinion!), however I had a problem.
I had a VERY large group (boneless with 1100 days) that I was converting from version 5.xx. During the 10-hour conversion the auto-update fired off and started downloading new headers - all 4 billion of them. Since I already had them I let the conversion finish and killed the updating thread from auto-update. However, on the next auto-update it again wants to download all 4 billion headers. The StorageData.db3 is about 26GB so I know the headers were converted, it just appears that the "last known header number downloaded" got screwed up by the auto-uprate rather than the conversion. (Yes, in hindsight I should have disabled auto-update before the convert from 5.xx - let that be a warning to all!)
Can I have it reset that flag to the highest (most recent) header in the database so I can avoid re-downloading the headers for the next 3-4 days?
I had a VERY large group (boneless with 1100 days) that I was converting from version 5.xx. During the 10-hour conversion the auto-update fired off and started downloading new headers - all 4 billion of them. Since I already had them I let the conversion finish and killed the updating thread from auto-update. However, on the next auto-update it again wants to download all 4 billion headers. The StorageData.db3 is about 26GB so I know the headers were converted, it just appears that the "last known header number downloaded" got screwed up by the auto-uprate rather than the conversion. (Yes, in hindsight I should have disabled auto-update before the convert from 5.xx - let that be a warning to all!)
Can I have it reset that flag to the highest (most recent) header in the database so I can avoid re-downloading the headers for the next 3-4 days?