Sounds like maybe metadata is out of sync, can you try removing /mnt/daos0/*, starting the server and then (on a separate tty) reformatting with "dmg storage format --reformat"?

Hello Richard "ERROR: DAOS I/O Server exited with error: /usr/bin/daos_io_server (instance 0) exited: exit status 1” indicates that there might be some useful information in the io_server log for the

We upgraded from SPDK v19.04 to v20.01 shortly after releasing DAOS 1.0, that would be my best guess as to the cause (obviously not if you a testing with 1.0 rather than master).

We probably need to get further information from NSG folks on product specifics regarding Opal support in 905p SSDs. This seems to be a prerequisite for device management through SPDK. Tom

There have been some fixes in master for build issues with ubuntu 20.04 (specifically for spdk, ipmctl and I think hwloc). Can you try building from master? Tom

Hello Gert Out of curiosity , what is your operating system and kernel version? Regards, Tom Nabarro – DCG/ESAD M: +44 (0)7786 260986 Skype: tom.nabarro

The bug with the storage reformat command has been fixed by Mike on master. Apologies for the inconvenience. Regards, Tom

You probably need the server log from the access point rank (/tmp/server0.log default setting in server config) to help debug the issue. Tom

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

That’s the one . thanks

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 (I’m usin

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 protobuf-c/ ./autogen.sh ./configure --prefix

Hello Anton This looks like maybe a mismatch between binary versions if it’s not a permissions issue. Make sure you're running daos_{server,admin} from the same build/install and instructions for sett

This is something that could be added but is not yet present, we would need to add the work item and prioritise but it’s not currently in the schedule. Regards, Tom Nabarro – DCG/ESAD M: +44 (0)7786 2

Not currently, only one pmem device is supported per IO server and only the one specified in scm_list will be used. Do you have a specific use case/scenario in mind for the blacklist? Tom

So when you use ctrl-c we are unceremoniously SIGKILLing the IO servers (graceful shutdown currently doesn’t work for various reasons and the control plane change to enable it was reverted). The syste

In my daos_server.yml file the nr_hugepages parameter is now set to 8192. This resulted in 16384 pages being allocated, because each SPDK run (2 daos_io_servers) allocated 8192 pages. The comments in

That’s unexpected, I will try to reproduce over the weekend.

Trying to gauge usage of the “—recreate-superblocks” option, does anyone rely on it? If anyone is could you please provide your use case. It is a developer shortcut to avoid the need to run “dmg stora

Best bet with these kind of issues is to get the privileged helper binary (daos_admin) log file which can be enabled by setting the server config helper_log_file parameter to a given path. This will g