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.
-
|
Can you please update to a current release? That version is from 2020 and a lot has changed. I don't know what's going on but I don't want to keep debugging such an old release. |
Beta Was this translation helpful? Give feedback.
-
|
I understand that. I'll update when I've got a bit of time to mess with it some more and hopefully things will change for the better. Thanks for your time! |
Beta Was this translation helpful? Give feedback.
-
|
You can't trust versions in the distro. They never update them regardless of bugs in the version they originally grab. That's why the first thing I ask in the support section is to check problems against the latest release. I have no control over what is packaged. Only my own releases. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I see. I'll give the latest release for Debian bullseye a shot. |
Beta Was this translation helpful? Give feedback.
-
|
I installed mergerfs 2.35.1 and it's behaving as I expected now. Following the same steps described above, the test directory is created on branch 1, so I suppose this was an issue with 2.31.0 and not something configuration related. Everything is working as I want it to now, so thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
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
mspmfsas 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 0The 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 onbackup4as 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
backup1and select that branch before it can find a match onbackup4by walking up the tree, but instead it seems it selectsbackup4anyway.Beta Was this translation helpful? Give feedback.
All reactions