this post was submitted on 24 Mar 2025
898 points (98.1% liked)

linuxmemes

24240 readers
1520 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. ๐Ÿ‡ฌ๐Ÿ‡ง Language/ัะทั‹ะบ/Sprache
  • This is primarily an English-speaking community. ๐Ÿ‡ฌ๐Ÿ‡ง๐Ÿ‡ฆ๐Ÿ‡บ๐Ÿ‡บ๐Ÿ‡ธ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    898
    Man I miss those classy RedHat ads from the sixties (lemmy.world)
    submitted 1 week ago by renzev@lemmy.world to c/linuxmemes@lemmy.world
    117 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] possiblylinux127@lemmy.zip 26 points 1 week ago (3 children)

    What's the problem with btrfs really?

    It is nice but it also feels like it is perpetually unfinished. Is there some major flaw in the design?

    [โ€“] swab148@lemm.ee 34 points 1 week ago (3 children)

    Mostly just the RAID5 and 6 instability, it's fantastic otherwise. But I'm kinda excited to try out bcachefs pretty soon, as well.

    [โ€“] RustyNova@lemmy.world 6 points 1 week ago

    Me too. (And when the author gets a chill pill)

    [โ€“] photonic_sorcerer@lemmy.dbzer0.com 2 points 1 week ago (3 children)

    So one should use ext4 for RAID 5&6?

    [โ€“] Trainguyrom@reddthat.com 5 points 1 week ago (1 children)

    Honestly, if it's important enough to RAID, it's important enough to do right and run full fat ZFS.

    You could also go the mdadm route with individual disks but ZFS pools are so battle-tested that whatever unholy edgecase you manage to create will almost certainly be something someone has encountered before, and it's probably well documented somewhere how to recover from

    [โ€“] photonic_sorcerer@lemmy.dbzer0.com 2 points 1 week ago

    Sweet, thanks for the info

    [โ€“] possiblylinux127@lemmy.zip 1 points 1 week ago

    I would use ZFS

    [โ€“] az04@lemmy.world 0 points 1 week ago

    I'm not an expert but I'd say mdadm with btrfs on top

    [โ€“] possiblylinux127@lemmy.zip 1 points 1 week ago (1 children)

    Isn't bcachefs in danger of being removed from the kernel?

    [โ€“] swab148@lemm.ee 3 points 1 week ago (1 children)

    Just gotta hope Kent gets his pull requests there in time lol

    [โ€“] possiblylinux127@lemmy.zip 5 points 1 week ago

    The Linux kernel uses mailing lists so technically it is called a patch.

    I think the biggest issue was that Kent had/has a attitude problem. It feels weird to pick a fight with Torvalds since he is kind of known for destroying devs but Kent did it anyway.

    [โ€“] enumerator4829@sh.itjust.works 18 points 1 week ago

    Iโ€™ve seen ZFS in production use on pools with hundreds of TBs, clustered together into clusters of many PBs. The people running that donโ€™t even think about BTRFS, and certainly wonโ€™t actively consider it for anything.

    • BTRFS once had data corruption bugs. ZFS also had that, but only in very specific edge cases. That case was taken very seriously, but basically, ZFS has a reputation for not fucking up your bits even close to BTRFS
    • ZFS was built and tested for use on large pools from the beginning, by Sun engineers from back when Sun was fucking amazing and not a pile of Oracle managed garbage. BTRFS still doesnโ€™t have stable RAID5/6.
    • ZFS send/recv is amazing for remote replication of large filesystems.
    • DRAID is kind o the only sane thing to do with todays disk sizes, speeds and pool sizes.

    But those are ancillary reasons. Iโ€™ll quote the big reason from the archwiki:

    The RAID 5 and RAID 6 modes of Btrfs are fatally flawed, and should not be used for "anything but testing with throw-away dataโ€.

    For economic reasons, you need erasure coding for bigger pools, either classic RAID5/6 or DRAID. BTRFS will either melt your data in RAID5/6 or not support DRAID at all.

    [โ€“] blackstrat@lemmy.fwgx.uk 3 points 1 week ago (1 children)

    The main one is how it handles corruption. It has actively been designed to do the exact opposite of what a sane filesystem should do and maximises downtime.

    [โ€“] possiblylinux127@lemmy.zip 1 points 1 week ago

    It shouldn't be that hard to patch it so that it works around failures. I'm not sure why that doesn't seem to be a config setting.