• mogoh@lemmy.ml
    link
    fedilink
    arrow-up
    51
    ·
    1 month 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
      31
      ·
      1 month 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
          9
          ·
          1 month ago

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