Replies: 1 comment 8 replies
-
Without you providing me very precise information about what is there and what happened one step at a time I have a hard time helping here. mspmfs works like described in the docs. It considers only the branches with the relative base path to the file to be created and if all branches are filtered out it walks back one level and tries again. If you're claiming this isn't happening then please provide a thorough step by step to reproduce. I just tested it myself and looks to work as expected. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello!
I recently discovered mergerfs and, since it fits my use case perfectly, I tried setting it up. It's great software and I managed to get it working, but I haven't been able to configure it to distribute new files as I would like. I read the documentation and believed I had found the options I needed, but it seems I was wrong. I want to keep this as short as possible, so I'll just describe my setup and how I'd like it to work.
First, I am running mergerfs 2.31.0, from the Debian stable repos.
I have 4 drives with their mount points added as branches. 3 of them are 8TB drives and contain many files from before I was using mergerfs, the 4th drive is a new 10TB drive which was new and empty when added. Since the first 3 drives already contain a manually organized file structure, I would like mergerfs to add new files to branches 1 to 3 if those paths already exist there, and if a path doesn't exist or a drive fills up it can go to branch 4, on the new and empty drive. For this reason, I chose
mspmfs
as the create policy, as I understand it will choose the branch which contains the path, before going up a level and trying again if it doesn't find a match.After reading the documentation and following the basic setup recommendation, I ended up with this in fstab:
/mnt/bank/backup[1-4] /mnt/merge/backup fuse.mergerfs allow_other,use_ino,cache.files=partial,dropcacheonclose=true,category.create=mspmfs,moveonenospc=true 0 0
The mount works, but new files aren't being distributed as I expected. For instance I created a new directory through mergerfs under a path which only exists on branch 1 (on
/mnt/bank/backup1
) and expected to find it underbackup1
, but instead the whole missing path tree was created onbackup4
as well, which again was a new, empty drive. There were still over 2TB free on backup1, so it didn't run out of space. I don't understand why it was created on branch 4 and not branch 1 in this case.What am I doing wrong or misunderstanding here? As I understand, mspmfs should get a match on
backup1
and select that branch before it can find a match onbackup4
by walking up the tree, but instead it seems it selectsbackup4
anyway.Beta Was this translation helpful? Give feedback.
All reactions