Hi Johann! I'm sorry I mixed up with mount point and POSIX is working fine, so I've deleted my previous messages. Right now I'm facing issues with dfs API in ior test. Heres new

Hi Anton, Are you able to create files manually under the dfuse mountpoint? Does ior work with file per process (-F)? Cheers, Johann From:<daos@daos.groups.io> on behalf of

[root@sky08 ~]# mpirun --allow-run-as-root -np 1 ior -a=DFS -b 1G -w -r -o /mnt/dfuse/testFile_dfs -t 128k -k --dfs.pool $dpool --dfs.svcl 0 --dfs.cont $dc ont --dfs.prefix /tmp/dfuse/ -G

Hi there, Please find attached a small test that you can compile as follows: $ gcc -o test -L${DAOS_PATH}/lib64 -I${DAOS_PATH}/include -ldaos -lgurt -ldaos_common -luuid ./test.c And then

Hi Adam, AFAIK there is no C++ binding but one for C ;-) [1] Unfortunately, the link to the Doxygen documentation does not work, but I used the native API successfully. Since the header files [2]

Hello everyone, Is there a starting C++ example (with its relative CMake file) that writes and reads data with the DAOS API? Thanks a lot. Cheers, Adam

Johann and Niu thanks a lot! I'll try to test it and send result to this topic!

As pointed out by Niu, the main gap is really on the DAOS control plane (i.e. dmg storage scan & support in the yaml config file). SPDK has built-in support for a NVMe-oF initiator/host

So far DAOS server supports only local PCIe attached NVMe, but it won’t be very difficult to support NVMeOF in the future, it requires only server configuration changes, all others are transparent

Our partners at Intel said that it's possible to connect NVMe disks by NVMeOF with DAOS. Could you explain how to do this? Thanks!

Thanks everyone for the help! I've created container and pool, mounted with dfuse, stored file, unmounted, mounted again and everything is fine! Thanks!

daos_server.log full of this debug: 09/16-15:04:12.07 apache512 DAOS[13572/13608] vos DBUG src/vos/vos_iterator.c:279 vos_iter_probe() probing iterator 09/16-15:04:12.07 apache512 DAOS[13572/13608]

Hi Anton, Yes, I think it is fine. You probably leaked pools from prior runs that show up in pool listing while the test is assuming that no other pools are present. I think you are good to go.

Can now reproduce locally and working to find a solution.

I've set new sizes, and launch only management test : [root@sky08 ~]# export POOL_NVME_SIZE=16 [root@sky08 ~]# export POOL_SCM_SIZE=8 [root@sky08 ~]# mpirun --allow-run-as-root -np 1 daos_test -m

Hello, This basically means there are not enough servers to run rebuild tests, so they were being skipped. The failure here is probably due to the incorrect usage of cmoka, which are used by

You'll want to turn on debug (see the troubleshooting section in the user guide) to get more information on why this failed. Also, the pool size (both SCM and NVME) will not be large enough to

I've set this env vars: export POOL_SCM_SIZE=2 export POOL_NVME_SIZE=4 And this is mine output before an error: REBUILD12: rebuild send objects failed setup: creating pool, SCM size=2 GB, NVMe

I've installed MOFED 5.0.2 on both hosts, and openmpi. And it works a little further! I've launched daos_test like mpirun --allow-run-as-root -np 1 daos_test. There were passed and failed tests, but

Hello Gert, I can’t see anything obviously wrong with bringup and hugepage allocation, did you reboot the nodes (just as a sanity check)? The next steps I will take is to get in touch with