Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Allow mergerfs.balance to exclude target path/disk #103

Open
undaunt opened this issue Jun 26, 2020 · 0 comments
Open

Feature: Allow mergerfs.balance to exclude target path/disk #103

undaunt opened this issue Jun 26, 2020 · 0 comments

Comments

@undaunt
Copy link

undaunt commented Jun 26, 2020

Our prior conversations are here and here

Allow mergerfs.balance to exclude a disk or path from being a target of data moved during the balance process

Use case:

disk1 (3%) - VHS content
disk2 (90%) - VHS content
disk3 (90%) - VHS content
disk4 (1%) - Docker volumes, databases, etc.

Disks 1, 2, and 3 contain /VHS root folder, Disk 4 does not. Mergerfs is running with a path preserving policy, such as empfs.

If running mergerfs.balance, I'd like to be able to exclude any data from being moved to disk4. Since balance is not path preserving, I can't currently prevent it from creating the VHS folder on disk4, but if I can exclude disk4 from being a recipient of any transferred data, this is possible, regardless of it not respecting path preservation.

@undaunt undaunt changed the title Features: Allow mergerfs.balance to exclude target path/disk Feature: Allow mergerfs.balance to exclude target path/disk Jun 26, 2020
lordyod added a commit to lordyod/mergerfs-tools that referenced this issue May 31, 2022
Allows the user to exclude one or more branches from the targets
selected by mergerfs.balance. For example, `mergerfs.balance -b
/sda /mnt/mergerfs/sda` will cause mergerfs.balance to remove `/sda`
from the list of `srcmounts` before beginning the balance operation.

Fixes trapexit#103

Signed-off-by: Lord Yod <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant