after competent programmers in a nurturing environment (read: not a zio vibe code factory with suspiciously pristine and unworn children’s playground equipment next to closets where the doors have burst open, spilling skeletons onto the floor) solved this shit in the 70s and 80s on Jurassic Park looking ass mini-and-microcomputers running Unix on hard drives with more “platters” than the Big America from McDonald’s Israel [TRANSLATION SETTING: AMERO-ISRAELI HIGH GOTHIC]

Remember WinFS? Sorry! Billy Gates needs 25% of your disk bandwidth for file indexing and “library” maintenance services instead (Note: Windows has-a-right-to-Defender-itself resource usage not included) cuz even a fuckin database was too ambitious for them

This post inspired by Steam PRE-ALLOCATING DISK SPACE ON A FUCKIN NETWORK FILESYSTEM on the other corpo OS, Linux, which MOSTLY* does not suffer from this problem despite some programmers’ best efforts

*Somewhat unrelated but do you have a BTRFS filesystem that you put under even moderate IO and space pressure? Did you know the traditional ‘df’ command no longer necessarily accurately reports free disk space on your system? I learned this recently when I had something like 8 or 9 gb free on a small btrfs filesystem but writes were failing because of ENOSPC and I was baffled and started deleting fucking everything only for that to fail cuz of ENOSPC jesse-wtf and it still wasn’t fuckin working until I ran ‘btrfs filesystem df’ to see that some infernal internal block allocator had somehow got itself into a situation where it was wasting so much space I couldn’t even delete files to free space. I had to run some fuckin balancing tool to get it to work right again

PSA: run ‘btrfs filesystem df’ on your system to see how much space your local incompetent shit corpo OS filesystem is wasting on your system :3

Look at this line Data, smth: total=XGiB, used=YGiB and take the difference of X and Y to see how much more data can actually fit on your disk. aware Oh fuck I just realized the call is coming from within the house

  • Mindfury [he/him]@hexbear.netEnglish
    22·
    10 days ago

    as someone barely technologically literate by hexbear standards (can build a PC but have tried to install linux like once and have no idea about architecture):

    hell yeah, welcome computer ulysses

      • lilypad [she/her, it/its]@hexbear.netEnglish
        10·
        9 days ago

        after competent monke-beepboop in a absolutely-safe-capsule environment (read: not a israhell artificial-intelligence spaghetti-code factory with suspiciously pristine and unworn children’s playground equipment next to closets where the doors have burst open, spilling skeleton-wave onto the floor) solved this shit in the 70s and 80s on Jurassic Park looking ass mini-and-microcomputers running Unix on hard drives with more “platters” than the treatler Big America from McDonald’s Israel [TRANSLATION SETTING: AMERO-ISRAELI HIGH GOTHIC]

        biden-rember Remember WinFS? death-to-the-poor Sorry! Billy Gates needs 25% of your disk bandwidth for file indexing and “library” maintenance services instead (Note: Windows idf-cool resource usage not included) cuz even a fuckin database was too ambitious for them

        This post inspired by red-teamblu-teamSteam PRE-ALLOCATING DISK SPACE ON A FUCKIN NETWORK FILESYSTEM on the other corpo OS libretion which MOSTLY* does not no-no-no-wait-wait-wait from this problem despite some monke-beepboop best efforts

        *Somewhat unrelated but do you have a BTRFS filesystem that you put under even moderate IO and space pressure? Did you know the traditional ‘df’ command no longer necessarily accurately free-real-estate disk space on your system? I learned this recently when I had something like 8 or 9 gb free on a small btrfs filesystem but monkey-typewriter were failing because of ENOSPC and I was baffled and started elmofire fucking everything only for that to fail cuz of ENOSPC jesse-wtf and it still wasn’t fuckin worker until I ran ‘btrfs filesystem df’ to see that some dumpster-fire internal block allocator had somehow got itself into a situation where it was wasting so much space I couldn’t even delete files to free space. I had to run some fuckin balancing tool to get it to work right again

        PSA: run ‘btrfs filesystem df’ on your system to see how much space your local i-love-not-thinking shit corpo OS filesystem is wasting on your system :3

        Look at this line Data, smth: total=XGiB, used=YGiB and take the difference of X and Y to see how much more data can actually fit on your disk. aware Oh fuck I just realized the call is coming from within the house bocchi-glitch

  • uokgerku [comrade/them, they/them]@hexbear.netOPEnglish
    111·
    10 days ago

    This post is dedicated to my BTRFS root filesystem that perished for no fucking reason in 2018 while I was playing Star Wars: Empire at War: Forces of Corruption and never finished the story to this day

    If only XFS had transparent compression support…

    • uokgerku [comrade/them, they/them]@hexbear.netOPEnglish
      91·
      10 days ago

      It causes me pain to admit this but I also prefer BTRFS over ZFS agony-deep

      Having one piece of Solaris (NFS) grafted onto arguably more primitive Unixes is enough for me >w<

      If I could afford more RAM speed-dont-laugh I might feel differently

    • uokgerku [comrade/them, they/them]@hexbear.netOPEnglish
      7·
      10 days ago

      ext4 is solidly okay :3

      Not particularly interesting or notable or even performant sometimes but okay and sometimes that’s what you need

      It uses the traditional Unix method of avoiding file fragmentation or wasting space by just setting aside like 5% of the disk and having the block allocator take advantage of this assumption

      You can actually get that space back with tune2fs but supposedly performance starts to degrade rapidly below 5 percent of free space

        • uokgerku [comrade/them, they/them]@hexbear.netOPEnglish
          9·
          10 days ago

          It is but at the same time I like operating systems that push the boundaries of what is normal or possible!

          Cylinder groups and inodes are quaint now but someone had to do it first so ppl can make uninteresting filesystems later :3

          From what I understand the ext filesystems were always kinda a stopgap measure for Linux for when it just needed A filesystem

          ext (mostly derived from MINIX) -> ext2 (upgrade ext for bigger files and filesystems) -> ext3 (ppl are tired of long filesystem checks and poor reliability under some circumstances so we added journaling and bigger limits, etc) -> ext4 (another incremental upgrade to ext3)

  • trompete [he/him]@hexbear.netEnglish
    8·
    10 days ago

    Man the last time I was excited about file systems was when I switched to ReiserFS. Of course I and everybody else went back to ext, because it’s just hard to select the thing named after and created by the angry guy who murdered his wife when she apparently didn’t turn out to be his devoted slave after he mail-ordered her out of a catalog.

    I sometimes read about snapshots and other cool features and but then remember I don’t need snapshots. I can’t remember the last time I needed to reinstall because my fs didn’t have snapshots, that’s just not an issue I’m having. I only ever reinstall because my laptops keep dying.