New Question

CephFS Windows mkdir error

asked 2023-03-14 16:07:40 +0200

alasdair-haig gravatar image

updated 2023-03-14 16:09:54 +0200


I've been getting an error while testing CephFS for Windows.

My setup is fairly small. I set up the Ceph service on a single VM, and then mounted a CephFS volume on one of my Windows 10 build agents. The error comes when performing a sync with a Perforce client to the mounted drive, and it outputs between near a hundred of these. I don't think the issue lies with the Perforce client, since it works fine a local drive, but it's hard to tell. I was hoping to get more info from the event viewer, but it doesn't know the error is either.

The Perforce log outputs this contradicting statement:

Can't create directory for X:\path\to\file.uasset

mkdir: X:\ The process was successfully ended

Event viewer is giving this error:

The description for the Event-ID "2" from the source "ceph-dokan" was not found. Either the component that triggers this event, not locally installed on this computer, or the the installation is damaged.....

[Time Stamp] ... 1b 2 ceph-dokan: WinCephCreateFile /path/to/file.uasset: Not found.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2023-03-15 13:11:24 +0200

lpetrut gravatar image

updated 2023-03-16 10:32:45 +0200


What happens if you manually create that folder, i.e. by issuing a mkdir command?

The following isn't necessarily an issue, it just means that a client attempted to open a file that does not exist.

[Time Stamp] ... 1b 2 ceph-dokan: WinCephCreateFile /path/to/file.uasset: Not found.

The following arguments can be passed to ceph-dokan to enable verbose Dokany logging. Note that the Dokany lib only uses console logging.

ceph-dokan.exe -l x --debug --dokan-stderr

Ceph can also be configured to use stderr logging by specifying the following in your ceph.conf file:

    log to stderr = true
    debug client = 2

In most cases, this should be enough to pinpoint issues that may arise from invalid paths, denied permissions, wrong or unsupported create flags, etc. If really needed, you can bump the client (cephfs) log level to 20. The log might become extremely verbose, in which case you might want to use a log file:

    log to stderr = false
    debug client = 20

    log file = C:/ProgramData/ceph/out/$name.$pid.log



edit flag offensive delete link more


I've created a file through the file explorer and had no issue, though I didn't try it over the command prompt with mkdir. I've had to steal the storage for this project for another urgent case, but I will try increasing the log verbosity as soon as I can and check back here.

alasdair-haig gravatar imagealasdair-haig ( 2023-03-17 20:27:16 +0200 )edit

Update: I've managed to find a solution with block storage instead of file storage, at the moment with iSCSI since it is what our present hardware solution supports (Synology). After implement block storage successfully into production, I plan to test this issue while migrating to Ceph rbd-wnbd.

alasdair-haig gravatar imagealasdair-haig ( 2023-04-03 21:29:08 +0200 )edit

Thanks for the updates, keep us posted.

lpetrut gravatar imagelpetrut ( 2023-04-04 09:37:57 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2023-03-14 16:07:40 +0200

Seen: 152 times

Last updated: Mar 16