Im using NFS mounted file system (AWS Storage Gateway) to store records.
I dont have any problems using COMPOSED, all files are writed fine by openvidu docker recording in my NFS mounted directory.
When i changed to INDIVIDUAL, the recordings appear in original directory, i need to umount my dir and enter in the same directory to get them.
Is openvidu recording INDIVIDUAL based on a physical memory address or something?
In OpenVidu CE, files are written directly to disk by Kurento Media Server.
In OpenVidu PRO, files are transferred from media nodes to master node using a Java process.
Nothing special. If you manage to solve issue, please share with us.
Regards
Updated kernel 5.3.0-1023-aws to 5.3.0-1028-aws (Ubuntu 18.04.4 LTS) and it seems to be solved.
I will still do some tests, any news I will post here.
Thank you very much Micael
Thank you… so it seems a kernel issue? Amazing 
It was not a problem related to the kernel … it ended up happening again intermittently after the update.
What I did to solve my difficulty was after mounting the NFS drive, restarting the Openvidu service.
The composed recordings work by writing to the NFS disk correctly because when the composed container is started the drive is already mounted.
For the individual ones, I believe that after the reboot, Openvidu started to point to the internal directory before the HD was mounted,and consequently recording on the internal disk. That was the reason of composed recordings being written to the NFS and the individual on the same mount directory, but internally in the machine.
Thanks for your usual help!