Hi Johann, Currently I'm testing some features of DAOS on the servers with CentOS 7.7 installed. I can test the socket provider on Ubuntu 20.04 after the test is done. I'll let you know if it works or

Hi Johann, I've seen the problem also in v1.1.2 on Ubuntu 20.04. I reinstalled CentOS 7.7 on the server machine, and as your experiment showed, the problem has gone now. I guess there is a compatibili

Hi Johann, Yes, I'm using "ofi+verbs;ofi_rxm". I guess the problem is independent to the DFS, since issuing small DFS IO showed no errors. Thanks, Yunjae

It seems to be related to the size of the file. When creating a file smaller than 4k, reading the file using cat fails.

Hi, I created a POSIX container and mounted at /mnt/dfuse on the client node, and ran the following command: ``` # echo "foo" > /mnt/dfuse/bar # cat /mnt/dfuse/bar ``` But it gives me the following er

Hello! Could you try using the mountpoint different from container path? Afaik, the path given to `daos cont create` is used as an alias to the container. Yunjae

Thanks for the quick reply, Patrick. I was also wondering how small the I/O size should be to go to SCM rather than NVMe. I'll test performances following your advice. It helped me a lot.

Is there any way to check if an object is allocated in SCM or NVMe? I installed DAOS in a simple server with Intel DCPMM and NVMe SSD, and I want to compare the I/O performance of the both two cases.

Same problem here, I used the master branch of daos on ubuntu 20.04.1 I also met this error when starting the daos_server: The same message was printed in /tmp/daos_server.log: The identify error also