I'm porting an existing application to use DFS (DAOS v2.0.2) instead of POSIX and need help understanding the error messages printed to the console. The code is using dfs_lookup() to retrieve the stru

Mohamad Thank you for the sanity check regarding dfs_lookup. After a little sleuthing, the application (evidently) was modifying the effective UID/GID around the time of that lookup. And it was this *

I've been experimenting with extending a pool but don't quite understand the results. Any insights would be most appreciated. The cluster is running with DAOS v2.0.2 and consists of a client and a pai

# dmg pool query kiddie Pool 700bf1b6-38b8-467e-9f91-7131138210ba, ntarget=32, disabled=0, leader=0, version=18 Pool space info: - Target(VOS) count:32 - Storage tier 0 (SCM): Total size: 60 GB Free:

Wangdi When I checked this morning, the pool had been idle four days, but the values from daos_pool_query() have not changed. As for object class, I'm not sure. Pool creation didn't specify a class. H

Thank you, Niu After thinking about what you said and running some additional experiments, I believe everything is working as you described. I created a 500 GB pool and added a POSIX container. After

If the space change isn't caused by reservation, what else might be causing this? What other things might I check?

Apologies. I was wrong. The space drops with pool creation, not with container creation. Creating a pool # dmg pool create --ranks=0,3 --size=500G kiddie Creating DAOS pool with automatic storage allo

The DAOS documentation has a good overview of its fault model. We are starting to experiment with various types of failures (pull a drive, pull a network cable, pull a power cord) and are curious what