It has been a while since I last saw a kernel backtrace😊 Never seen this before. I assume that this happens during pool deletion or disconnect? Cheers, Johann From:<daos@daos.groups.io> on

We had an oops occur today, backtrace is below. When I started looking, I see there are 6 of these over the last month, the backtrace is always the same. It seems to be happening in DAX. Does

The easiest way, assuming you want a single KV per container is to do the following: import pydaos cont = pydaos.cont(‘<pool_uuid>’, ‘<container_uuid>’) kv =

Hi Johann, this is on Slackware Linux (https://en.wikipedia.org/wiki/Slackware). It's still actively maintained, but it's a very old distribution so often times there are modern things missing. In any

Ok, regarding KVObj, my naive attempt was:import pydaospydaos.KVObj() And that obviously fails due to missing positional arguments. I didn't realize on the factory-like mechanisms through the

Alex, Can you elaborate on what it is you’re trying to achieve? There are really two parts to the python bindings, there’s pydaos.raw which is using ctypes to open the daos client shared

I have a DAOS installation for evaluation/exploration and I was trying to make the Python bindings work. My first contact with PyDAOS is at the official documentation

Thanks for the report Jordan. I have just pushed a fix:https://github.com/daos-stack/daos/pull/2625 No, I’ve never seen this failing. Could you please advise what distribution you run?

Hi all, I recently updated my out-of-date DAOS installation to commit a7f093db2fc96aa1dc20cc8c293d44274474ef62 (I'm sure this wasn't the commit that changed this behavior, but good to have for

Alex, Well, I didn’t explain myself properly either. 😊. You should not need to set LD_LIBRARY_PATH to get things working, daos has code in it to find all the dynamic libraries it needs, so

@Kevan sorry I didn't explain myself properly: I "successfully" fixed my problem, but I was trying to understand if my fix was proper or if I had somehow messed up something in my installation. I am

Hi Alex, Does it still happen in latest master? The workaround was checked into master a couple of weeks ago. We changed the order of dlopen calls as there appeared to be some issue that

Alex, Try running daos_agent without your LD_LIBRARY_PATH settings, after first setting “export LD_DEBUG=all” and capture the output. Look for libgurt in the output, see where ld searched for

I had a similar issue as you (I think), and I solved it in the same fashion: the error banished as soon as I added those two path to the LD_LIBRARY_PATH in my .bashrc. In my scenario, the specific

Hello, Colin Yes, obj_update/fetch are obsolete, and obj_rw should be used for update & fetch. I will push a patch to fix it. Thanks for telling us. Thanks WangDi From: <daos@daos.groups.io> on

mjmac, Thanks for the heads up. Is there a JIRA or other place where the curious could get more details on the management service plans? Thanks, -Patrick

Hi Anton, You have several options to run performance benchmarks: FIO: Use dfuse + the interception library with stock libaio engine Use the dfio async engine for direct access without fuse

Hi all. In preparation for the upcoming replicated Management Service feature, a change has been made (a1e6b7c) to remove support for specifying the hostlist when issuing pool commands. The

Hi Anton, >> Is it real to check perfomance using mounting with dfuse and fio? I've read that interception library libioil is under development. I’d like Mohamad to comment on that. He can speak

It was: https://github.com/daos-stack/daos/blob/e80d0321f1deee43de61fd50350a08f142faa713/utils/rpms/daos.spec#L55 and the "build" Dockerfiles were updated with the new