• mogoh@lemmy.ml
    link
    fedilink
    arrow-up
    45
    ·
    23 hours ago

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

    • rtxn@lemmy.world
      link
      fedilink
      English
      arrow-up
      29
      ·
      23 hours ago

      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.

        • rtxn@lemmy.world
          link
          fedilink
          English
          arrow-up
          8
          ·
          22 hours ago

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

          • The_Decryptor
            link
            fedilink
            English
            arrow-up
            2
            ·
            4 hours 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.