Ceph large file transfer failures

edit

I have the save problem. I take some photo for log, could you please give a email? i will send photos to you. My email address is 295510979@qq.com

Hello,

we have the same problem. When the error occurs, our ceph shows "1 clients failing to respond to capability release" . I tried to get the logs. But the problem is, when i activate loglevel 3 then the error did not occur in the same way.
With log level 3 the servers shows "slow OSD operations". But it is not throwing any error.

When i start the client with the dokan debug options on, then a error ocours that never occured before:

###Create file handle = 0x000001D6D8DBE060, eventID = 0006, event Info = 0x000001D6CC02D4A0
###WriteFile file handle = 0x000001D6CC057A50, eventID = 0003, event Info = 0x000001D6CC02CF60
libc++abi: Dokan Information: SendAndPullEventInformation() with NTSTATUS 0x0, context 0xcc057a50, and result   object 0x000001D6CDB11010 with size 48
terminating due to uncaught exception of type std::runtime_error: invalid utf8Dokan Information:    DokanEndDispatchCreate() status = 0, file handle = 0x000001D6D8DBE060, eventID = 0006, result = 0x1
Dokan Information: SendAndPullEventInformation() with NTSTATUS 0x0, context 0xd8dbe060, and result object 0x000001D6CBFBBDE0 with size 48

###WriteFile file handle = 0x000001D6D7A2B720, eventID = 0004, event Info = 0x000001D6CC02D0B0

The original error occured in pacific and reef.

right now i use :

server 18.2.0
dokan 2.0.6.1000
client : https://ask.cloudbase.it/question/364...

I don't know if this is connected, or if this are totally different errors. But i thought i post it in case it is connected.

best regards
Benedikt

Hi,

Can you please send us the Ceph version (ceph-dokan -v)?

ceph-dokan can log to stderr, event log and/or a log file, here's a config sample: http://paste.openstack.org/raw/806450/. As shown there, raising the cephfs client log level to 3 might include some useful information.

Let's see if it's a Ceph error. If not, we can retrieve Dokany logs from stderr using the --debug --dokan-stderr arguments.

By the way, how reproducible is it?

Thanks, Lucian