Put the guest to 6.6-lts then. Good thing to change for a weird problem like this.
At the same time, your testing environment is more like your host.
Put the guest to 6.6-lts then. Good thing to change for a weird problem like this.
At the same time, your testing environment is more like your host.
Okey-dokey
ο ξ° ο ~ ξ° uname -r ξ² β
6.6.34-1-MANJARO
ο ξ° ο ~ ξ° lsblk ξ² β
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 40G 0 disk
ββsda1 8:1 0 40G 0 part /var/cache
β /var/log
β /home
β /
ββsda2 8:2 0 8M 0 part
sr0 11:0 1 1024M 0 rom
then open btrfs-assistant
ο ξ° ο ~ ξ° lsblk ξ² β
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 40G 0 disk
ββsda1 8:1 0 40G 0 part /run/BtrfsAssistant/c863c9b5-d87a-4196-bdfb-5002d20e4ce0
ββsda2 8:2 0 8M 0 part
sr0 11:0 1 1024M 0 rom
and close it
ο ξ° ο ~ ξ° lsblk ξ² β
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 40G 0 disk
ββsda1 8:1 0 40G 0 part /var/cache
ββsda2 8:2 0 8M 0 part
sr0 11:0 1 1024M 0 rom
ο ξ° ο ~ ξ°
Im not to worried. It looks like its just a bug in either btrfs assistant or lsblk. I donβt think its a problem with my actual mounts so i can just go without it, which is a pity.
I wonder if the dev knows, i may get around to posting on the gitlab (i donβt think i even have an account on gitlab, show how often i come across packages managed on there).
I suppose the point is that i like to get all my ducks in a line before i move over to my main system, this was a bit curious.