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.

Greetings, struct cont_snap_destroy_in { struct cont_op_in cei_op; daos_epoch_t cei_epoch; }; struct cont_snap_destroy_out { struct cont_op_out ceo_op; daos_epoch_t

Broken links fixed on master https://github.com/daos-stack/daos/pull/2654

That’s the one . thanks

This one? doc/dev/development.md From: <daos@daos.groups.io> on behalf of "Nabarro, Tom" <tom.nabarro@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Thursday, May 7, 2020 at

So apologies but that link is dead, anyone know where the contents got moved to? I can’t find any references to relevant content in the docs. The protobuf-c package is installed during build

This is a development tool so maybe it’s not pulled in by the default build. I installed as follows: git clone https://github.com/protobuf-c/protobuf-c cd

Hi Guys, In https://github.com/daos-stack/daos/tree/master/src/proto/README.md, it uses “protoc -I mgmt --c_out=../mgmt mgmt/srv.proto --plugin=/opt/potobuf/install/bin/protoc-gen-c” to

Hi, As the comments of co_post_reply (in cart’s api.h): /** * Collective RPC post-reply callback. * This is an optional callback. If specified,

Greetings, Is “co_aggeregate” operation called before or after “ca_post_reply” operation? Thanks. Colin

I am not sure, unfortunately, we didn’t notice when it first happened. We will keep an eye out if it happens again. Kevan From: <daos@daos.groups.io> on behalf of "Lombardi, Johann"

That looks much better. You should be aware that daos will be using a byte-array for the values, so in this case 42 will be a string, not a integer. It’s likely that you’d want to use

Thanks, I didn't know about pydaos.Cont and was a bit lost. I completely missed that section on the deployment documentation, shame on me. I was definetely looking at the wrong places, thanks for