Hi WangDi, commit 8200a7fb403e091b51b4b00c1aec57dafefb1ada [daos@hl-d106 scripts]$ daos pool list-cont --pool 96670dea-d357-4235-8659-dac16d01b1c2 --svc 40 [daos@hl-d106 scripts]$ … No

Hi, Server_group certainly seems a useful thing to add, service ranks I thought was scheduled for removal but would also make sense if it’s still in use. I can file a ticket and work on this as

Hi Colin, If the #cores is enough, to get best performance commonly can configure with one helper XS for each VOS target – in your case can setnr_xs_helpers as 16 if you configured with 16

Hi Guys, Currently, there are only three info set to duns attribute of UNS path. They are FS type, pool UUID and container UUID. It’s enough for dfuse since dfuse’s server group and service

Greetings, We currently set nr_xs_helpers to 0. We have defined 16 targets. That’s per daos_io_server. For best performance, what value should nr_xs_helpers be set? Also, consideration like

Hello, Colin I tried with this commit, and it can generate the failure message on my env. I assume you build the source yourself? And what is your output of “ldd install/bin/daos” ? Thanks WangDi

Greetings, commit 8200a7fb403e091b51b4b00c1aec57dafefb1ada Thanks. Colin From: <daos@daos.groups.io> on behalf of "Wang, Di" <di.wang@...> Reply-To: "daos@daos.groups.io"

Hello, Thanks. This does show the connection failed with –svc 40. I am not sure why it does not output any failure messages. But I do see others also complained about zero failure message. Which

Hi WangDi, Is this what you need: 05/14-09:53:00.86 hl-d106 DAOS[20928/20928] fi INFO src/cart/src/gurt/fault_inject.c:486 d_fault_inject_init() No config file, fault injection is

Hello Patrick, Well, this is really strange indeed. BTW, I am unable to reproduce when running with current master which is only 45 commits ahead of yours and none seem to be related… If problem

Hi, thanks for the tip! It seems that a "regular dmg storage format" doesn't do the trick, but appending "--reformat" resolves the issue. It runs fine now. Kind regards Ruben Am 14.05.20 um 09:02

Hi, I assume that you have run dmg storage format after starting the server and before creating the pool, right? If you don’t want to emulate any SSD, you should also comment out the bdev_*

Hi there, From your log: snode3: Starting I/O server instance 0: /usr/bin/daos_io_server snode2: daos_io_server:0 05/12-06:28:47.96 snode2 Using legacy core allocation algorithm snode2:

If 40 does not exist, it should not be able to connect to the pool at all, I.e. it should output sth like "failed to connect to pool: …”. These logs seems suggesting the pool connection did

Greetings, Executing the command: daos pool list-cont --pool a68b3845-fe78-481e-aa84-164e851d5f52 --svc 40 Note that 40 does not exist. We did not get an error from the daos command.

Hi there, I try to run DAOS in a real physical environment, but got problem. Below is the output when i try to start DAOS system with 3 storage nodes. do anybody help me. if need any informatino,

Hello, My setup and issues are very similar to what has been described in https://daos.groups.io/g/daos/message/317. I have tried every suggested fix from the corresponding thread and so far, none

Good morning, I'm running commit: commit 53b0c5ff3d45c8addfee11cbfd6dd49e6f88dc3e And the daos container create command is no longer giving any output on failure: [daos@hl-d102 ~]$ daos container

Hi Colin, This part could use some improvements indeed. The “in” and “out” structs are generated by macros from src/container/rpc.h: CRT_RPC_DECLARE(cont_snap_create,

Thanks you, Nabarro.