@kupan787 wrote:
Hello,
I recently installed bees in order to make use of the deduplication feature. One of the things it does is create a btrfs subvolume called .beeshome, where it stores some logs, a hashfile. This gets mounted at the root of the btrfs pool.
So for example, I have a btrfs pool called BackupPool. I then have a share inside of that called BackupShare. Rockstor mounts these as:
/mnt2/BackupPool
/mnt2/BackupShareAfter starting bees, it creates a subvolume under BackupPool so the structure looks like:
/mnt2/BackupPool/.beeshome
However, Rockstor picks this up, and treats it as a Share. So it also gets mounted under /mnt2 like:
/mnt2/.beeshome
It is also listed as a Share in the Rockstor GUI.
This wouldn’t be an issue, except that I have multiple pools. And if I run bees on each pool, I’ll have multiple .beeshome sub volumes (one per filesystem). I’m not sure what Rockstor will do, as it tries to mount all of these under /mnt2 as they will all appear to have the same name.
Ideally, it’d be nice if there was a way to tell Rockstor to ignore “shares” that aren’t created by Rockstor. Or if there was an interface to list subvolumes that rockstor should ignore. Or maybe even simply to just have Rockstor not mount sub volumes that start with a . (although not sure if that would cause other issues).
Posts: 2
Participants: 2