There was a regression in fsfsverify that prevented it from detecting overflowed windows when the instruction stream wasn’t corrupted. That has been fixed, along with a couple of other minor adjustments. The new version is up and ready for use!
I’ve been hard at work for the past couple of weeks, and I’m proud to announce that an updated fsfsverify script is available. Functionally, the only difference is the addition of svndiff1 support. Underneath, the great majority of the code has changed to make it easier to support different types of svndiff streams. It should also be easier to hack, if you find yourself needing to add a feature. Enjoy!
Things are going well on the fsfsverify front. I’ve run the new code through a number of tests, and it’s performing just as well as the old one. If this keeps up, I’ll have it out the door this week.
I’ve been hard at work on a new version of fsfsverify that handles the new svndiff1 format. I also took it as an opportunity to rewrite large portions of it, because it’s clearly leading a life of it’s own. So far it has seen 330 downloads by 278 unique ip addresses since June of last year. I’m sure many of those were people just curious about the script. However, I know people are indeed using it, since I get emails declaring success, and occasionally ones that ended in failure (hey, I can’t fix data loss).
One nifty feature on most modern macs is that you can disable processors on the fly. Up front, that doesn’t sound like much of a benefit, but in reality it is. As a developer, I can examine the compute time using different processor configurations, and see how well the software scales.