I noticed that it is not fixed, I can’t do a total btrfs-balance, this will produce a total mess with the boot/grub, I can’t boot to the system, I have to do a “sudo btrfs check --repair – init-extent-tree /dev/sdb1” again, but as I move the boot/grub, again without fixing it to another partition/filesystem by creating a partition exclusively to boot,
I can do:
sudo btrfs balance start -dusage=85 /
sudo btrfs balance start -musage=70 /, as is in the man btrfs-balance, which I did sometimes, without troubles.
I need to create a new partition in a already used one and I am afraid to do and messed it. I know this is not right, but I am with this rolling release a long time, and there is a lot of configs in it that I will loose if I did a new install and then the backup with rsync.
My btrfs is the simplest, does not have “dup” data, it is in a 120GiB SSD, with only the Manjaro system, which 53,2GiB is used, I don’t used it to make btrfs backups, no space fot this, the “/home” is in a different partition.
I think I did some things I shouldn’t, but it’s “working” anyway.