Tiered caching clarification about mergerfs HOT 7 CLOSED

I'll see about adding some additional details / examples to make it more clear.

from mergerfs.

I'll try implementing later today/tomorrow and bug you if i have more questions. Thanks again really appreciate it.

from mergerfs.

np, and thanks for the support. appreciated.

from mergerfs.

The cache pool is the pool with the cache filesystems, yes.

No, that wouldn't be proper fstab. You are mounting to the same location. And you put the /mnt/fast1 at the end of the list. As it mentions it should be first. Order matters.

from mergerfs.

What kind of setup do you have where this setup would be beneficial?

from mergerfs.

Thanks. Ok something like this then?

# slow + fast devices
/mnt/fast1:/mnt/slow1:/mnt/slow2   /mnt/media1    fuse.mergerfs <options>

# slow only
/mnt/slow1:/mnt/slow2              /mnt/media2    fuse.mergerfs <options>

The usecase is for a media server. I download files over usenet which can max out a 10Gb connection and write to nvme. Then, the slowest part is it takes forever to transfer the downloaded files to slow media storage. By allowing the new media to reside temporarily on nvme (tiered cache), media files would be accessible almost instantly and can be migrated to slow storage during the night for example.

from mergerfs.

Yup. That ordering is most important if you are using create=ff policy and want to spill over. Some people have different ideas/strategies though so.... at the end of the day it's just about having the pool you use generally which includes the cache focused branches and the other pool just to make migration easier. Could just as well be a bespoke tool but then the policies would all need to be added to that.

from mergerfs.