From:<daos@daos.groups.io> on behalf of Wu Huijun <huijunw91@...> Reply to: "daos@daos.groups.io" <daos@daos.groups.io> Date: Saturday, 6 June 2020 at 09:45 To: "daos@daos.groups.io"

Hi, I came across this DAOS object open mode enum. Will you support DAOS_OO_IO_RAND and DAOS_OO_IO_SEQ? How much performance gain we can get for random and sequential access respectively? /**

Thank you! From: <daos@daos.groups.io> on behalf of "Chaarawi, Mohamad" <mohamad.chaarawi@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Monday, June 8, 2020 at 12:25 PM To:

Hi Colin, The major advantage of using the l2g, g2l is performance. Doing a 1 per process call to connect / open is issuing an RPC to the server side, and pool / container operations are

Greetings, DAOS supports the conversion of handles local2global and global2local. What are implications if any, if each process just perform local connect or open? Pool/Container/Objects.

Colin, I’m referring to the “Unified Name Space” feature or workflow that DAOS supports, in essence this is managed through the setting or a extended attribute “user.daos” on entries in

Hi, Jiafu it do a environment variable related problem. I forgot to set OFI_INTERFACE and CRT_PHY_ADDR_STR env variables, since I opened a new terminal. thx for ur suggestion! 2

Yes, I’d spotted this might be a problem recently when looking at fuse commit history. Fuse started off with one prototype, then updated and we updated daos to match, then they more recently added

Hi there, We regularly test DAOS over DRAM (to emulate SCM). We found out that fallocate(2) isn’t always reliable over tmpfs and it is better to set “PMEMOBJ_CONF=prefault.at_create=1;” in

Hi, 1003 is invalid variable error. You can see the error code mappinghere. As talked, it should be related to your DAOS environment variables. Thanks.

Hi Hector, Timeout messages on a client side are a symptom of some issue, not the issue on its own. It basically means an RPC was attempted to be sent to the server and was not responded to within

Hi all, Has anyone tried the max scalability of DAOS while using DRAM to simulate NVDIMM? We continuously saw one or more server instances exited and several clients reported crt timeout when the

Hi guys, When I try to build and support spark and hadoop, I got a problem below. What should I do to solve this problem.

Hi all, We are currently playing with the code on GitHub master (cloned on June 4). We frequently received an error triggered in crt_context.c. It is saying that ctx_id 0 (status:0x38) timed out,

Hi Pitman and Colin, The problem was solved by put the mount point on a disk-based rather than memory-based file system. Do you know why this happened? Cheers, Hector Wu

Hi, Can you provide more information with regards to “special UNS file”? Thanks. Colin From: <daos@daos.groups.io> on behalf of "Pittman, Ashley M"

Could you send me the command line you’re using and the error message? It would help to run in foreground mode to diagnose this. We recently added a check for the mount point to be a special UNS

Hi guys, I used to be able to mount DAOS with dfuse. However, I failed to do the same with the latest DAOS code on GitHub. I got errors complaining the path is not in a unified DAOS namespace. Any

from the config, FUSE_USE_VERSION is defined to 32 reqs.define('fuse', libs=['fuse3'], defines=["FUSE_USE_VERSION=32"], headers=['fuse3/fuse.h'], package='fuse3-devel') from git fuse

Never mind .. I see it get set when building shared .. I am just trying to see how the Macros get expanded. From: <daos@daos.groups.io> on behalf of Colin Ngam <colin.ngam@...> Reply-To: