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.

[–] TheEntity 10 points 18 hours ago (1 children)

That should result in a sparse file on any sane filesystem, right?

[–] rtxn 8 points 18 hours ago (1 children)

Theoretically, yes. Theoretically NTFS supports sparse files, but I don't know if the feature is enabled by default.

[–] [email protected] 2 points 15 minutes ago

It supports it, but it's opt-in by apps.

Enabling compression is another option (Though with a speed and size penalty), it's user visible at least.