**** I do not mind deleting the post if seen confusing/wrong/unnecessary… ******
I will try BTRFS (Again!)
As per a discussion with @dalto some time ago, where at the end I promised I will read and learn more about BTRFS.
No need to mention again the problem of BTRFS+Snapshots causing Baloo to keep reindexing “/home”
After I learned a little about BTRFS (and even less about Snapper or Snapping in general) I thought I would just start and convert to BTRFS without taking or using/installing any snapshot software as a start point.
Why no snapshots? Just to avoid Baloo reindexing, to understand “practically” the BTRFS file system, then I can look at snapshots.
So, to start I will give you my current situation (next post), and a few questions (after next post), in hope I understand more and convert without messing up my system, and be ready later to use snapshots without any issues.
Why all of the above?
- Understood from @dalto that he actually uses BTRFS, Snapshots (including “/home”) without having any issues of Baloo reindexing “/home” while many snapshots of his "/home ar taken and not reindexed. So, why can’t I do it!
- The future of Linux is in BTRFS (I believe the future has already started but I am still back in time)
The benefits I am expecting from BTRFS without auto snapshots via Snapper or TimeShift:
1- File compression
2- Deduplication
3- (I hope I got it right), in EXT4 (assuming 1 SSD, total size 250GB, of which 50GB reserved for system you are left with 200GB for data, even if the system is taking actually only 10GB.)
In BTRFS there are two subvolumes (like partitions) one for system and the other for data where both their sizes change according to actual use. That is the system will be taking actually only 10GB not the full 50GB as in EXT4 and the rest (240GB) goes fully for data.
4- (Hopefully) I can start with doing a manual snapshot of the system ONLY without “/home”
Just for reference (like summarising) allow me to put a summary of our discussion below ( What is in parentheses ( ) is @dalto 's, what is not in parentheses is mine)
I Suggested BTRFS takes snapshots of only the file system not ‘/home’
(You decide which subvolumes you want to snapshot. )(Baloo has an easy UI which allows you to decide what you do and don’t want to index. Why can’t you simply exclude the snapshots?)
(This seems like a setup or a design issue to me. I have hundreds of snapshots of /home and none of them are getting indexed. I don’t even have them excluded by baloo.)
(If you put snapshots with user readable privileges inside the part of your system that baloo is indexing then that will happen.)
(((snapper makes the snapshot directories only readable by root so baloo would never index them.)))
(It looks like you might have been using timeshift.)
As you mentioned earlier that you already have BTRFS and Baloo and NOT having this problem reported by several users, so I may conclude that:
Baloo is perfect on its own.
BTRFS is perfect on its own.
To use them both needs the users to be a bit techie to “design” the system as you mentioned in a post above.(It seems that baloo triggers reindexing because of the way it identifies devices.)
I will try read more
********************* Here is my humble understanding **********
- a subvolume is like a separate drive
- a snapshot is like a copy of a folder or a subvolume
- a great feature is deduplication and compression.
- if i don’t take snapshots all benefit is compression
I would like to thank you all for your patience, your support, your understanding.
I hope you forgive me for this lengthy post and I hope I am not causing any trouble or breaking any rules.
I do not mind deleting this thread if you see it is unnecessary!
I am just trying to get the most out of my beloved EndeavourOS and my beloved community.
Thank you.