"no space left on device" - but config seems fine

[lockheed]

My setup is

Filesystem                                                                        Size  Used Avail Use% Mounted on
/dev/sdj                                                                          932G   33G  898G   4% /mnt/mergerfs_parts/seatage_1t_slimNdyin
/dev/sde                                                                          931G  890G   42G  96% /mnt/mergerfs_parts/wd_1t
/dev/sda                                                                          932G  930G  1.5G 100% /mnt/mergerfs_parts/samsung_1t
/dev/sdb                                                                          916G  874G   43G  96% /mnt/mergerfs_parts/hitachi_1t
/dev/sdf                                                                          932G  930G  1.6G 100% /mnt/mergerfs_parts/toshiba_1t
/dev/sdc                                                                          1.9T  1.1T  816G  57% /mnt/mergerfs_parts/samsung_2t_new
compound_data                                                                     6.4T  4.6T  1.8T  73% /mnt/storage

So, as you can see, plenty of disks with free space on it.

My fstab:

### MergerFS
/mnt/mergerfs_parts/* /mnt/storage fuse.mergerfs category.create=eplfs,defaults,allow_other,use_ino,moveonenospc=true,minfreespace=3G,fsname=compound_data 0 00

### MergerFS parts
UUID=13a64e56-70e7-44f2-b0b5-85b6225ca184 /mnt/mergerfs_parts/hitachi_1t ext4 defaults,noatime,commit=60,nofail 0 2
UUID=75f8771d-afb0-4ce9-b491-7b11c24c3d01 /mnt/mergerfs_parts/samsung_1t xfs defaults,rw,nofail 0 2
UUID=abd037d5-45f8-4cf2-9691-9495bcb779ae /mnt/mergerfs_parts/toshiba_1t xfs defaults,rw,nofail 0 2
UUID=39ba8877-e0e6-4982-845c-98a0d0493e42 /mnt/mergerfs_parts/wd_1t ext4 defaults,noatime,commit=60,nofail 0 2
UUID=ea0b3655-df5c-42d7-b8f2-414f14b1e322 /mnt/mergerfs_parts/samsung_2t_new xfs defaults,rw,nofail,noauto,x-systemd.automount 0 2
UUID=d10c100d-b500-4ec7-a1e7-40f9b9dc018c /mnt/mergerfs_parts/seatage_1t_slimNdyin btrfs noatime,nodiratime,compress=zlib:3 0 1

So from my recognition, everything should work fine. However, I am trying to copy a bunch of 2G files to /mnt/storage, I get
'No space left on device'

I tried with "category.create=epmfs", but to same result.

Any ideas?

[lockheed]

Ok, I found out the reason was that there was no directory path create for the subdirs those files were copied into.
So after creating them, files were transferred.

However, isn't there an automatic mechanism in which mergerfs would handle this without a manual intervention?

[trapexit]

You've chosen a policy that specifically is designed not to be automatic. That's the point of ep* policies. Check the policy docs. mspmfs or mfs or whatever it is you want.

[trapexit]

https://github.com/trapexit/mergerfs#filtering

If all branches are filtered an error will be returned. Typically EROFS (read-only filesystem) or ENOSPC (no space left on device) depending on the most recent reason for filtering a branch. ENOENT will be returned if no eligible branch is found.