-
Notifications
You must be signed in to change notification settings - Fork 672
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mounted network drive converting to Local drive when load is high #1252
Comments
Hi @dheeraj1729 , The drive cannot switch to local drive but I think what you see is that the request to get the volume information is slow and during that time the drive looks like that. I would suggest adding caching where possible to quickly complete the dokan requests. |
Hi @Liryna Thanks for the response, I’m exploring alternative approaches for implementing caching. Is there any way to control the wait time using a Dokan option in this scenario? |
Wait time is controlled by https://dokan-dev.github.io/dokany-doc/html/struct_d_o_k_a_n___o_p_t_i_o_n_s.html#ad953734dbc1baf170937eec8c1b4228b and https://dokan-dev.github.io/dokany-doc/html/group___dokan.html#ga1d5b0bf526fbf143a726fe1816fe7f15 if that's what you are looking for |
Closing for inactivity |
Feature request can skip this form. Bug report must complete it.
Check List
must be 100% match or it will be automatically closed without further discussion. Please remove this line.Environment
Check List
Description
I have an application that uses Dokan to mount a store located on a SAN drive. Occasionally, the mounted drive intermittently switches to a local drive. Although the issue can be reproduced using the mirror.exe tool, it does not occur consistently.
Steps to reproduce:
1.Mount a network drive.
2.Continuously refresh the File Explorer. Occasionally, the mounted drive will switch to a local drive if the load on network drive is high. (Another way to reproduce is by disconnecting the network drive after mounting)
Logs
dokan_local.txt
dokan_local1.txt
The text was updated successfully, but these errors were encountered: