• Kaityy
    link
    fedilink
    arrow-up
    4
    ·
    6 months ago

    for some reason i feel like i shouldn’t run that command

    • nebula42@lemmy.zipOP
      link
      fedilink
      arrow-up
      9
      ·
      6 months ago

      it creates a file with a size that’ll keep growing until you stop it, filled with garbage data. it makes it extremely easy to create a file of 50 gigabytes or so. it does it over the course of about 8 minutes or so, so it’s not like it’s filling your hard drive to the brim immediately.

      • Kaityy
        link
        fedilink
        arrow-up
        2
        ·
        6 months ago

        how does that work with the allocation of individual file sizes? Like what happens if you overflow your buffer before the system checks on it again to resize? or is that not possible/not a realistic risk factor?

        • nebula42@lemmy.zipOP
          link
          fedilink
          arrow-up
          5
          ·
          6 months ago

          it’s probably possible, but it’s not a realistic risk imo. i didn’t track exactly how much time it takes to fill up 50 gigabytes, in practice it probably takes longer, i was just eyeballing how long it took lmao