Linux · btrfs

btrfs offers compress=lzo, zlib, and zstd. How do they trade off, and when does compression actually make disk access faster rather than merely smaller?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in btrfs

When you modify a file on btrfs, what happens to the original disk blocks holding that data?

A colleague assumes btrfs is the universally adopted next-gen Linux filesystem. Where does the vendor picture actually diverge?

You suspect corruption on a btrfs filesystem and want to run a consistency check. What is the one hard precondition, and how do you actually make it repair errors?

You want to store a large database file or a VM disk image on btrfs without the usual COW fragmentation penalty. What do you set, and what is the catch on an existing non-empty file?

You mount a btrfs filesystem with compress=zstd and expect all existing files to shrink. Which files actually get compressed?

In btrfs terms, what is a subvolume, and how is it different from just making a directory?

Start learning today

Free to start — download the app or use it in your browser.