X_STORAGE_KEY_CONFLICT
Means
the key collides with another key on a local or memory disk
Typical cause
the local driver stores an object as a file at its key, so one key cannot be both an object and the directory of another: put('a') then put('a/b'), or the reverse — or a beside a.json/b, which collide in the sidecar tree. Refused before a byte moves; it was a bare ENOTDIR / EISDIR. s3Driver and memoryStorageDriver hold both
Fix
disk("<disk>").list({ prefix: "a" }) with the name the disk is registered under — lists the object in the way (the cause names it); store one of the two under a different key