Closed SpiderUnderUrBed closed 2 weeks ago
Change to the directory containing the .beeshome
folder, then:
mv .beeshome .beeshome.old
btrfs sub create .beeshome
rsync -av .beeshome.old/. .beeshome/.
rm .beeshome/beeshash.dat # because the subvolumes differ
You didn't recreate the subvolume structure of your system while moving your data to a new partition.
bees will crawl all your data from scratch, expect some increased disk IO for a few hours or days. Also, expect bees to increase disk usage slightly during this time before finally cleaning up, so keep enough free space.
If everything works, you can remove .beeshome.old
.
I am getting this issue:
[spiderunderurbed@daspidercave:/run/bees/mnt/0095faf2-2359-4515-a1e1-af7ef6f11a0f]$ btrfs sub create .beeshome
ERROR: not a btrfs filesystem: .
[spiderunderurbed@daspidercave:/run/bees/mnt/0095faf2-2359-4515-a1e1-af7ef6f11a0f]$
Which is strange because
It seems like /run/bees/mnt/ uses tmpfs, any way to change this in plasma or beesd? I am getting a whole host of issues.
/run/bees/mnt/...
is only mounted while bees is running - and bees exits immediately because of the error. So try mounting subvolid=0 first:
mkdir /mnt/btrfs-pool
mount -o subvolid=0 UUID=0095faf2-2359-4515-a1e1-af7ef6f11a0f /mnt/btrfs-pool
Now try my above steps in that directory.
It seems like /run/bees/mnt/ uses tmpfs, any way to change this in plasma or beesd? I am getting a whole host of issues.
/run
is meant to be tmpfs, it's used for private runtime data and will be discarded on reboot. Services like bees create a private mount inside which is not to be used by you. To modify your btrfs, mount it manually, or run a more verbose lsblk
command to find it's mount point. .beeshome
must be present at the root of subvolid=0
- your standard btrfs mount point may not show that.
Sorry for the late response. Anyways.
mkdir /mnt/btrfs-pool
mount -o subvolid=0 UUID=0095faf2-2359-4515-a1e1-af7ef6f11a0f /mnt/btrfs-pool
This works while my system is up and running, but I was trying to make it execute before my system starts, with no avail, and this fix doesn't come without its own issues. So is there a underlying problem which can be addressed?
Here was my attempt at making a permanent fix:
fileSystems."/mnt/btrfs-pool" = {
device = "UUID=0095faf2-2359-4515-a1e1-af7ef6f11a0f";
depends = ["/" "/mnt"];
fsType = "btrfs";
options = [ "subvolid=0" ];
};
(note I use nixos)
Is there a issue with some recorded data I need to delete so it can recreate .beeshome?
Simply btrfs sub create /mnt/btrfs-pool/.beeshome
. If it exists already, rename it first.
I made a few mistakes trying to clear out /mnt/btrfs-pool which lead to me requiring to re-install my system, regardless, the issue is fixed now.
I had to move all my stuff to a new partition to fix it, now beesd is not working, I am getting this error:
I tried a series of commands, making a .beeshome on /, making bind mounts between /run/, trying to make subvolumes, nothing works
I also wrote the issue here: https://www.reddit.com/r/btrfs/comments/1fgzu6w/beesd_has_a_issue/