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

linuxmemes

24150 readers
3358 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. Even if you watch it on a Linux machine.
  • 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 17 points 6 days ago* (last edited 6 days ago) (1 children)

    The CoW nature of Btrfs means it's often slower than ext4 for common tasks, right? It also means more writes to your SSDs.

    I've stuck to ext4 so far, as someone who doesn't really have a need for snapshotting.

    Edit: I'm not an expert on file systems in the least, so do chime in if these assumptions are incorrect.

    [–] [email protected] 7 points 5 days ago (1 children)

    Meh, ssds are basically cow by nature anyway, you have to erase large blocks, you can't just rewrite into them.

    [–] [email protected] 1 points 5 days ago (1 children)

    But if the file system needs extra writes anyway for CoW, and the SSD needs its own CoW, then wouldn't that end up being exponential writes? Or is there some mechanism which mitigates that?

    [–] [email protected] 4 points 5 days ago (1 children)

    The fs does cow then releases the old block if appropriate.

    The ssd has a tracking map for all blocks, it's cow relies on a block being overwritten to free the old block.

    Basically it works out the same either way.

    [–] [email protected] 2 points 5 days ago (1 children)
    [–] [email protected] 1 points 5 days ago* (last edited 5 days ago)

    It's interesting, however, if you mkfs.ext4 without -E ssd, or through some weirdness in your driver chain the filsystem doesn't know it can discard, then everything everywhere sucks for everyone, a cow fs is worse because no blocks are ever overwritten till the end, and the block map becomes a disaster while performance goes down the drain.

    Nowadays this rarely happens outside of very broken USB mass storage chips.

    This is why we used to have the fstrim command.