FYI. If you need any help, feel free to ping us😊 Subject: IO500 SC20 Call for Submission Call for IO500 Submission Deadline: 30 October 2020 AoE Stabilization period: 1st October -- 9th

Really sorry for the spam, but I used the wrong timezone when creating the invite☹ The last one that was sent to the mailing list (attached for reference) is the correct one. Cheers, Johann

Johann Lombardi changed the Webex meeting information. When it's time, join the Webex meeting here.

Hi there, Please find below the Webex meeting invite for the DUG’20. The agenda will be posted there: https://wiki.hpdd.intel.com/display/DC/DUG20 Cheers, Johann

Johann Lombardi changed the Webex meeting information. When it's time, join the Webex meeting here.

Johann Lombardi invites you to join this Webex meeting. Meeting number (access code): 130 258 2165

I've tried to change daos_nvme.conf in runtime of daos server and before starting due to connect disk through rdma. In both ways I cannot see it in daos_system. nvme discover see exported disk. When

This specific issue is different appears to be at the dfuse/fuse kernel module level. I note you’re using a newer fuse driver than I am (7.31 vs 7.23) and also a newer libfuse3 as evidenced by the

This case is different, the mount point here has not been used to create a container so dfuse is attempting to use the pool and container on the command line. The error reported is a DAOS error

Hi, This is the same issue as Gert hit last week, specifically that you’re providing the pool/container UUIDs twice to dfuse, one via the path and once on the command line. The fix in this case

I'm experiencing (most likely) the same issue since a week or more on the master branch. I reproduced it on today's master branch on Ubuntu 20.04. Verified a few days ago on Centos

Thanks for the response, I tried again with: dfuse --mountpoint=/home/daos/container/ --svc=0 --pool=[pool_id] --container=[container_id] --foreground This led to the following

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

Hello! I am trying to use dfuse to create a POSIX-enabled mount. My container is created thusly: daos cont create --pool=[pool_id] --svc=0 --type=POSIX --path=/tmp/mycontainer I then try to mount

The issue is gone after adopting Kennth’s suggestion to set “crt_timeout: 1200” in global area of daos_server.yml instead of under “servers/env_vars”. @Cain, Kenneth C, thanks!

Hello Jaifu, Can you try to set the server RPC timeout by using the daos_server.yml file crt_timeout setting (and not using the env_vars section with the CRT_TIMEOUT variable)? See

The most recent worked commit I can track is 681b827527a0587d8496d3adbbd77a175370766c (Feb 28).

I just recalled that I re-opened the ticket on Aug 10. The issue has been existed for long time. Please see detailed info in the ticket.

Hi Jiafu, What was the previous commit that you know of that works in your setup? Thanks, ~~Alex.

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.