(⬤ᴥ⬤) to [email protected] • 16 hours agoefficient game design rulelemmy.blahaj.zoneimagemessage-square37fedilinkarrow-up1623arrow-down113cross-posted to: [email protected]
arrow-up1610arrow-down1imageefficient game design rulelemmy.blahaj.zone(⬤ᴥ⬤) to [email protected] • 16 hours agomessage-square37fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink42•15 hours agoYeah, that does not add up, you are right. There must be several error or it must include the stacktrace or something.
minus-square@[email protected]linkfedilinkEnglish28•15 hours agoIt’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.
minus-square@[email protected]linkfedilink10•15 hours agoThat should result in a sparse file on any sane filesystem, right?
minus-square@[email protected]linkfedilinkEnglish7•14 hours agoTheoretically, yes. Theoretically NTFS supports sparse files, but I don’t know if the feature is enabled by default.
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.