Greetings, When a Client makes an IO Request, is the endpoint the IO Server or the Target? Thanks. Colin

Hi Mohamad, okay I think that clears up everything, thanks very much! The second question was regarding using DAOS-VOL to write data into DAOS and afterwards mounting the container with DFS to check

Hi Ruben, I wouldn't call this requirement "new" as it has been there for a long time now. But yes when using a DFS container (MPI-IO, dfuse, hdf5 over posix or MPI-IO), the container must be of type

Hi Mohamad, thanks for the tip, I had not created the container as POSIX-type. I remember that this wasn't explicitly necessary somewhere in the past, is this a new behavior? The "POSIX Namespace"

Hi Ruben, I assume you create the container with type POSIX? daos cont create --pool=$DAOS_POOL --svc=$DAOS_SVCL --type=POSIX and that succeeds and you pass that cont uuid to the dfuse

Hi, I'm still failing to get the DAOS Fuse filesystem running. I'm using the daos_server_local.yml config with DAOS v0.9 and have server and agent running. Both the high level and low level Fuse

Thanks a lot Patrick! From:<daos@daos.groups.io> on behalf of "Farrell, Patrick Arthur" <patrick.farrell@...> Reply-To: "daos@daos.groups.io" <daos@daos.groups.io> Date: Thursday 2 July 2020 at

Johann, Patch worked just fine - able to mount, etc. Thanks much. Regards, -Patrick

Thanks Patrick! The SPDK team came up with this patch: https://review.spdk.io/gerrit/c/spdk/spdk/+/3156 Would you mind giving it a try please? If this works, we will get the process started to

As suspected, the SSDs are now coming online normally. Let me know if there's any further troubleshooting the SPDK team would like. -Patrick

Heh, yes! These are among the lines I was planning to try to remove, so will do. It is interesting to note of course that SEND_RECV is reported by the tool Gert had me using, but that's not a total

Hi Patrick, I talked to the SPDK folks and they suggested to try removingline 1464-1470 in module/bdev/nvme/bdev_nvme.c: - if (spdk_nvme_ctrlr_get_flags(nvme_bdev_ctrlr->ctrlr)

Hi Colin, I think this is coming from FIO with their latest ‘atomics’ patch in the latest master. You can change the fio version to their latest release (3.20) and recompile to fix this

Hi Colin, What platform are you building on and do you know what prerequisite component is being built when you get that message? Sounds like a bug in that component’s configure script. In

Greetings, What GCC version is required for building daos v1.0.0? Just want to verify as I am getting: .. In file included from crc/crc32c.h:23:0, from

Greetings, What GCC version is required for building daos v1.0.0? Just want to verify as I am getting: .. In file included from crc/crc32c.h:23:0, from

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).

Gert, Thanks for the further information. Something I don't quite follow: "The product specification lists both Pyrite as Opal support, what is less clear in the documentation is that Opal is not

Patrick, Colin, I verified with the NSG Business Unit that builds the 905P SSD. The product specification lists both Pyrite as Opal support, what is less clear in the documentation is that Opal

Recall that we have used this SSD with DAOS in the past. Whatever is preventing this now is a change, perhaps in SPDK but possibly in how DAOS is invoking it. Regards, -Patrick