51 points
Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
31 points
It’s possible that the log writer wanted to fseek to the end of the file and write something, but the target pointer value was somehow corrupted. Depending on the OS, the file might end up having a fuckton of zeroes in the skipped part.
10 points
9 points
Theoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
