this post was submitted on 23 Mar 2026
87 points (97.8% liked)

Linux

13047 readers
327 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] forestbeasts@pawb.social 10 points 1 week ago (10 children)

btrfs subvolumes are cool, but I'll still take partitions for separation. The whole point of having a separate home partition is that it's separate from / if we have to, say, reinstall the OS, or the filesystem breaks or whatever.

sure it might be possible to install an OS into a btrfs subvolume without wiping other subvolumes, but do I wanna risk it? Nah.

-- Frost

[–] Illecors@lemmy.cafe 22 points 1 week ago (4 children)

That... Is literally how you do it. You install the system onto a subvolume. Or many, in fact - the way I do. Root, var, srv, home, opt all get their own subvolume. Only boot stays as a separate partition.

[–] fruitcantfly@programming.dev 9 points 1 week ago (3 children)

Ignoring /boot, what is the benefit of putting everything else in different subvolumes? As opposed to just one subvolume for / and one for /home, which is what I currently have. It just looks to me like it’d be extra work, but I’m probably missing something

[–] infiniteface@programming.dev 4 points 1 week ago* (last edited 1 week ago)

For one thing if you're snapshotting your subvolumes for backup purposes then it will ignore nested subvolumes. Eg you dont want to preserve snapshots of huge installed game directories, cache directories, logs or docker / podman images, usually. Saves a lot of space.

Also you can tune copy on write on a subvolume, which is great for some use cases for performance.

load more comments (2 replies)
load more comments (2 replies)
load more comments (7 replies)