Will you try appending ${MY_DAOS_INSTALL_PATH}/lib64 to your LD_LIBRARY_PATH and re-run the “make” command? export LD_LIBRARY_PATH=${MY_DAOS_INSTALL_PATH}/lib64:$LD_LIBRARY_PATH ~Dalton

Hi, $ cat ${MY_MFU_BUILD_PATH}/src/common/CMakeFiles/mfu.dir/link.txt /usr/bin/cc -fPIC -I/home/daos_agent/git/daos/build/include -L/home/daos_agent/git/daos/build/lib64/ -luuid -ldaos -ldfs

Interesting. As you said, the libraries are in fact there. And I think cmake is finding the libraries, or else cmake would print something like “/usr/bin/ld: cannot find -ldfs” before getting to

Hi, yes, "build" is where daos is installed. $ ls -l /home/daos_agent/git/daos/build/lib64/ total 22080 drwxrwxr-x 3 daos_agent daos_agent 4096 Dec 13 08:06 daos drwxrwxr-x 2 daos_agent daos_agent

Is this directory correct? /home/daos_agent/git/daos/build/lib64/ Libraries are usually in the “install” directory, not “build”. Is “build” in fact where daos is installed?

On Tue, Dec 28, 2021 at 03:13 AM, Bohning, Dalton wrote: grep -B 2 "CMAKE_SHARED_LINKER_FLAGS:" ${MY_MFU_BUILD_PATH}/CMakeCache.txt Hi, I run your command and it prints as follows: $ grep -B 2

Apologies, my previous command snippet was muddled. Correction: $ grep -B 2 "CMAKE_SHARED_LINKER_FLAGS:" ${MY_MFU_BUILD_PATH}/CMakeCache.txt //Flags used by the linker during the creation of shared

Hello, It looks like most of the libraries specified by “-luuid -ldaos -ldfs -ldaos_common -lgurt -lpthread” are not linked. Something to keep in mind is that “CFLAGS=… LDFLAGS=…

Hi, The design is to ensure that all IO requests from different pools are processed in FIFO order, and space pressure from one pool doesn’t interfere request processing for other pools, but the

solved at 23 Dec at the agent.yml, edited the interface numa from "1" to "0", though there is no port under numa 0, but it works at last.

Hello, Everyone! Now all update/fetch requests of pools are in sched_info->si_fifo_list. If a pool request exceeds req_kick_limit, will it also block other pool requests? thanks!

Hi, I built MFU according to https://daosio.atlassian.net/wiki/spaces/DC/pages/4874571083/IO-500+ISC21 but encountered some "undefined reference" errors. [ 39%] Linking C executable

All, We are pleased to announce that DAOS 2.0 release is now generally available. This release brings support for the following features: Erasure code¶ Telemetry and monitoring¶ Pool and

Hi guys Hi I am using the daos system with mellanox card, tyring to test roce my system is centos and daos 2.1.100, libdaos 1.6.0 cause many failures, i let the server and client in one server,

Hi there, Please find below the DAOS community newsletter for December 2021. Past Events (November) SC’21 Tutorial (Nov 15) Practical Persistent Memory Programming: PMDK and DAOS Adrian

Hi, Allen The log showed it was stuck on creating blobstore. It looks like your device isn’t well supported by SPDK, could you collect some device information by SPDK ‘identify’ tool? Also,

Hi Tom, I reduced the variables according to your suggestion, but there is still the same error. Regards, Allen

The failure seems to be happening when creating the blobstore but just to reduce variables, can you try with the following env_vars: env_vars: - CRT_TIMEOUT=300 - CRT_CREDIT_EP_CTX=0 And

Hi Tom, Yes, please check the previous reply. --------------原始邮件-------------- 发件人："Nabarro, Tom "<tom.nabarro@...>; 发送时间：2021年12月3日(星期五)

Did you manage to get the engine log with DD_MASK=all, that will give us more information about why the engine is not completing start-up (and why you don’t have any joined ranks reported by "dmg