You can monitor the output of pool query that reports the space usage on PMEM and SSD separately. That been said, we don’t have a metric reporting the total amount of data migrated by aggregation

Is there a way to know how much data has been migrated from PMEM to SSD

Extents smaller than 4KiB that cannot be aggregated with other contiguous extents remain in PMEM and are not migrated to SSDs. As for overwrites, extents that are eventually not readable any longer

Thank you very much for your answer! I have another question: whether all the data written to PMEM will be written to SSD, for example under Zipfian workload, if the data still in PMEM is overwritten

By default, any contiguous extents strictly smaller than 4KiB are written to SCM and the ones bigger than or equal to 4KiB are written to SSDs. The 4KiB threshold is configurable starting DAOS v2.0

In this case, the core problem is that there is an empty storage tier in the configuration, and the config parser doesn’t handle this correctly. Createdhttps://daosio.atlassian.net/browse/DAOS-12826

Hi there, scm prepare is only required when using Optane PMEM. Since you use DRAM, you don’t need to run scm prepare. That being said, it would be great for scm prepare to fail nicely in this

I'm trying to set up daos 2.3.103 using the EL8 Dockerfile but I ended up with this error when trying to run scm prepare this is what my configuration file looks like I also tried this with the

How does DAOS decide whether to write data to SSD or PMEM？

Tianzy, Good to hear it is working now, however in general reboot should not be needed after applying those sysctl settings; dual_iface_server test also worked before... I wonder if there was

Alex, For some reasons, my cluster rebooted. After that, I tried what you have said. My issue is fixed! I guess after applying

Can you change log_mask: debug in daos server yaml file and provide logs from all engines involved? On a client side please provide ofi logs by doing export FI_LOG_LEVEL=warn before running

1、 https://docs.daos.io/v2.0/admin/predeployment_check/#setup-for-multiple-network-links Lombardi had pointed out it and I had done it. 2. the test: Any further suggestion?

Hi Tian, I noticed that you are running 2 engines per node. Did you follow this guide in order to set sysctl settings

CART didn't work

It makes progress either, but it still failed. client01: On storage01: 03/03-08:17:03.29 storage01 DAOS[13113/0/614] daos INFO src/engine/drpc_progress.c:278 drpc_handler_ult() dRPC handler ULT for

That’s progress! IIUC, you have 5x 3.8TB = 19TB per engine, so 20TB is probably too much. Could you please try with a smaller nvme-size? Since you use 2.2, you could also run “dmg pool create

Lombardi, Glad to see your response! I followed https://docs.daos.io/v2.2/admin/predeployment_check/#multi-railnic-setup, error is changed from DER_HG(-1020) to

I see, so it looks to me same to the question 4 of "append write"? Hope my answer is helpful. Thanks -Niu

Q3：I mean ROW(Redirect-on-write ) . Thanks -Lin