atop writes to corrupted file after system hang

[arjenlentz]

After a system hang/crash/whatever, atop just continues writing to file for the current day.
But atop -r bombs out at the point-in-time where the crash happens when browsing with t/T or jumping with b.

So, either atop needs to scan current file on startup and if needed fix it up so that appending more to it is actually readable later, or for instance use magic record headers so that a corrupted file doesn't hinder reading.

[er013]

Or as a last resort, rename old file and continue with new-current file.
(Just ran into that issue after my swap exhaustion, sent basically same suggestions to author from atoptool.nl contact page)