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

196

16721 readers
1887 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

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

Yeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.

[–] [email protected] 30 points 3 months 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 3 months ago (1 children)

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

[–] [email protected] 9 points 3 months 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 3 months 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.