Mergerfs seems to neglect one disk

Hi,

I am using mergerfs with a pool of 4 disks. I am using the policy "existing path, most free space" and the additional options "defaults,allow_other,direct_io,use_ino,ignorepponrename=true".

Now three of the disks are 86% full, their usage history looks as in attachment "data4". But one disk is only 76% percent full, the usage history is in Attachment "data1". As you can see, even when the usage of the other disk increased heavily during last December, there is no real change for Disk 1.

At first I expected the "existing path" policy to be the problem, but this is *not* the case: the directory where all the new files go is present on every disk.

Any idea what could be the reason for this behaviour?

Hi trapexit,

I finally managed to dig a bit deeper and found the following:

When new files are created in the pool, it never happens on Data1. Occasionally, a new directory is created on Data1, but without the containing files; instead, the directory is also created on another drive in the pool (with the files). So it is possible to write to the file system.

I added some screenshots of the mounted files, the file systems, and the mergerfs configuration.

Edit: I also added a screenshot of a newly created directory: The directory is created on both Data1 and Data4, but the files are written to Data4 (although it has less free space).

Does this behaviour make any sense to you?

But the path *is existing* on both volumes! If you look at the last screenshot: The directory written to is "Media/News". A new directory for the new file is generated on Data1, but no file is written to it. Instead, the same directory is generated on volume "Data4", where the files end up being stored.

Sorry if I sounded irritated - I didn't mean to yell, I only meant to emphasize, and I do appreciate your help.

I will try to give a better example tomorrow.

OK, while trying to reproduce the behaviour, I believe I finally managed to find the cause: The "News" directory, where all the new files go, actually exists an all file systems, but the "temp" directory, which is used for incoplete downloads, does *not* exist on "Data1". So the download starts on one of the other volumes, and after completion of the download, the file stays on the same volume, even when it's moved to another directory. So I guess you were right after all.

Thanks again for your help!