this post was submitted on 19 Sep 2024
735 points (97.8% liked)
196
16279 readers
2334 users here now
Be sure to follow the rule before you head out.
Rule: You must post before you leave.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
It's possible that the log writer wanted to
fseekto 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.That should result in a sparse file on any sane filesystem, right?
Theoretically, yes. Theoretically NTFS supports sparse files, but I don't know if the feature is enabled by default.
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.