Steffan,

What you’re doing is correct, and the results are mostly as expected.  DAOS does not yet support pool and container enumeration although this is being worked on, once the feature is in DAOS then we’ll add support for it to dfuse, for the time being the readdir call in dfuse will return directory contents for directories that represent something within a container, and ENOTSUPP for pools and the root if you’re launching without the -p and -c options.

I would caution against using a subdirectory in /mnt/daos for mounting fuse, it’ll probably work but I think the DAOS server assumes that it can write files with any name to that directory so I’ll be lower risk to use a different mount point to avoid any confusion.

Once dfuse is up and running you should be able to call stat on any entry and see results, ENOSSUPP is what I’d expect if you ran ls on /mnt/daos/fuse on your example below.

Finally, it’s possible to launch dfuse in “singleton” mode which means you can launch it directly without the use of orterun, this is often easier but you need to run the server with a -a flag and set DAOS_SINGLETON_CLI=1 and CRT_ATTACH_INFO_PATH=/path in the dfuse environment

Ashley,