On Oct 25, 2019, at 11:20 AM, Justin Will <[email protected]> wrote:
> I agree with Tim. This is a flag inside the datafile. > > I wish a utility existed again to just clear the flag. I have tried to > find this in the datafile a few times without luck. With a feature like this you are playing russian roulette. You don’t know the state of the data file if the flush did not finish. There could be important blocks in the data file that are not correct and could lead to other problems like causing 4D to crash. Pull the trigger and maybe you don’t crash, maybe you do. And maybe you don’t crash immediately but you damage the data file more and slowly. Dangerous game. John had a crashing problem when running MSC to just “repair” his data file. MSC would crash trying to do a “repair”. Some blocks were “damaged” or not updated correctly due to the flush not finishing and it was causing MSC to crash. Probably record address table blocks or allocation bitmap blocks were not right. So the only fix John could use was the old “recover by tags” method. Which worked and that’s exactly why it’s there for situations like this. I think we are much better off with the current implementation. If the cache flush does not finish exactly how 4D expected, you can’t trust the data file. You need to do an MSC to make sure everything is OK and immediately fix any issues found. And if your data file is big and MSC takes too long, you can always restore the last backup and integrate the current log file. John was using a Time Machine backup and not a 4D backup, which is a completely different type of backup and one that cannot be totally trusted like you can with a 4D backup. Time Machine could have been copying the data file at the exact time a flush was happening and not pick up every data file change. Tim ***************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ***************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
