Looking at various btrfs videos, I never see example, where one ext4 data partition would be on the same disk, where is btrfs. Is this normal setup or it is not advisable to go this route?
If btrfs and ext4 on same disk is ok, what order should I have, btrfs before ext4 or other way around?
Also, I’m used on regular systems, to set up partitions first with gparted, then I start installer and through it, I’m assigning partitions. How should I proceed here? Should I do all the steps within installer? Or I can set up btrfs system and subvolumes with gparted? What is suggested, best, simplest route?
This is going to be my first time ever going out of ext4 world. My setup will be simple, no encryption, no compression, nothing extra or fancy
No problem my $HOME partition is ext4 and the EFI partition is vfat, on my other machine desktop I have btrfs, ext4 and ntfs partitions for data that is shared with an old windows installation, note that my $HOME is partition 4, partition 5 btrfs was created after resizing partition 4, however I avoided moving it to the correct position as my important data is there, so the order of creation doesn’t really matter.
Thank you! This extra data desire is probably result of me not quite understand the whole thing I typically (on ext4) have multi boot, 2-3 installations each with home, then I have one separate data partition for all the data and each install have access to this data partition. Then I have another disk, where is a copy, backup of data partition. That way I have data on two disks.
May I ask you one more question, as someone who created that btrfs helper. From view point of someone completely new in btrfs world, (I don’t even know what are default settings, beside I need to have root and home subvolumes), would your helper be beneficial for complete noob or would be better to get familiar with btrfs first? I plan to use timeshift for simplicity.
Thank you, I see there are all kind of possibilities.
I plan to have home as default (btrfs subvolume), just thinking of separate data partition. Still not sure the route I will go. Less I complicate, better should be he-he
Btrfs Assistant is designed to make btrfs and snapper easier to use.
Snapper has always been a far more functional solution than timeshift for btrfs snapshots but it’s complexity made it hard for many users. Btrfs Assistant attempts to give you flexibility of snapper with the simplicity of timeshift.
Of course, it has expended over time so now it also contains some functions for advanced users. However, keeping it easy to use has always been part of the focus.
There are some reasons Btrfs is useful for some parts of Home.
Configurations are accidentally changed incorrectly somewhere in home directory, e.g. KDE environment looks crooked and difficult to adjust manually. Rollback with snapshot is a solution.
Malware example “WannaCry” targets only home data and encrypts or corrupts all documents and data in home directory. Rollback could help.
Using btrfs send/receive or btrbk to create multiple home backups to other disks and is faster and more efficient than EXT4 with rsync
Non-essential heavy data is a large part of Home example ISO in Downloads, multimedia, VM images and Steam games. They go to other partition EXT4 and are mounted with Home, they don’t need to be processed by Btrfs balance and snapshot creation.
What compression level do you apply/recommend? Can we have different compression levels for home and root?
I currently have a single home subvolume that I snapshot. This idea is of carving up home is awesome. Because mostly I just want to roll back my .config subvolume. How do I go about carving up home now i.e. can we do this after the installation?
Thank you everyone, lots of good info to process and to learn.
I got my btrfs system installed, all looks good.
Will install brfs-assistant next and start playing around.
This is testing disk, just for this learning purposes, so I don’t have to be too careful
And I got an answer to another question - so you can have multi boot within btrfs, cool, will try that to one day…