• Brkdncr@lemmy.world
    link
    fedilink
    English
    arrow-up
    48
    arrow-down
    2
    ·
    1 day ago

    Looks to be region specific and occurs on specific controllers under heavy writes (50gb+). Symptoms clear after a reboot.

      • BombOmOm@lemmy.world
        link
        fedilink
        English
        arrow-up
        24
        arrow-down
        1
        ·
        edit-2
        1 day ago

        50GB of write is pretty easy to get to. That is a single game download. (and remember, it unpacks at the same time, a 50GB download is more like 125GB of total write)

        So, if you own an affected drive, gotta be really fucking careful using Steam on Windows.

      • KingPorkChop@lemmy.ca
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        10
        ·
        1 day ago

        But it gives the religious cult a chance to knock on your door and ask if you’ve heard of their lord and saviour, Linus.

  • CubitOom@infosec.pub
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    6
    ·
    1 day ago

    I sure hope nobody recommends me to use a free and open source operating system that never has issues like this over this proprietary OS that I’m used too and have been paying licensing fees for since I started using computers.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      26
      arrow-down
      2
      ·
      1 day ago

      Linux has had its fair share of nasty bugs

      The difference is that you are unlikely to be affected unless you are running a very recent untested kernel.

      • chaogomu@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 day ago

        I live dangerously with my fully up to date Arch box.

        But I also have an LTS Ubuntu box that’s been humming away in the background for about the last five-ish years? Just a quiet little file server, doing its job and being ignored.

    • Nougat@fedia.io
      link
      fedilink
      arrow-up
      14
      arrow-down
      5
      ·
      1 day ago

      LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX LINUX

    • al_Kaholic@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      1 day ago

      Because you got older and realized just because your teachers and parents wasted their money now that you’re an adult there a better way?

      • Vik@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        I’ve only recently been made aware of btrfs’ tendency to completely fuck data at failure states.

        I’ve been using that filesystem on fedora for maybe two years now without issue, though I suppose I don’t regularly find myself hitting the issues required to cause these problems.

        • NaibofTabr@infosec.pub
          link
          fedilink
          English
          arrow-up
          4
          ·
          22 hours ago

          Well yeah, like the article I linked says:

          It has now been nearly eight years since the “experimental” tag was removed, but many of btrfs’ age-old problems remain unaddressed and effectively unchanged. So, we’ll repeat this once more: as a single-disk filesystem, btrfs has been stable and for the most part performant for years. But the deeper you get into the new features btrfs offers, the shakier the ground you walk on—that’s what we’re focusing on today.

          So if you’re just using it for your PC hard drive you’re probably fine. The problem is that BTRFS is intended to provide similar features to RAID and ZFS, but that’s where it starts failing.

  • tim@infosec.pub
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 day ago

    More 24H2 shittery. I locked all my Windows machines to the 23H2 track after installing it on my desktop completely broke all networking functionality.

    • rdri@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      23 hours ago

      At my workplace 23H2 specifically causes most of unbootable situations where bootloader has to be repaired in some way or another.

      • tim@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        23 hours ago

        Strange. I’ve had zero issues out of 23H2 and I update it religiously.

        • rdri@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          22 hours ago

          Same here with updates but it might be caused by use case and hardware. E.g. most of users use laptops and a lot of them have vPro functionality. Exact source of the issue is not identified but these two are best candidates in my opinion. If you are using a basic home PC then none of it affects you.