this post was submitted on 19 Sep 2024
718 points (97.9% liked)

196

16245 readers
2330 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 29 points 2 days ago (1 children)

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.

[–] [email protected] 11 points 2 days ago (1 children)

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

[–] [email protected] 9 points 2 days 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 1 day 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.