-
Notifications
You must be signed in to change notification settings - Fork 650
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
Problem in the mirroring of files when they are read using memory mapping io. #1110
Comments
@grandemk Sorry for the long delay. |
Hi, I didn't change the mirror sample. Mostly, some sizes of the file Test1.txt trigger the bug, so I just tweaked the content of Test1.txt until the bug occured (with, for example the file I linked). From what I remember, I talked about correlation because I could get two path of execution in the Mirror Sample when I read the content of the file:
While tweaking the content of Test1.txt to trigger the bug, I would only see 2. This would be called only one time, and then subsequent Read wouldn't show any calls to the Mirror Sample Dokan API Implementation, as if the information was cached before the user space driver and wasn't correctly invalidated in some case (probably related to some kind of rounding in page size, as writing enough data would at some point invalidate this cache and the correct data would be read.) |
Environment
Check List
Description
Hi :)
The changes done in the root directory of the mirror do not seem to be mirrored in some cases related to memory mapping.
The change in the size of the file is detected, but the content is wrong at the end of the file.
This problem appears in the mirror default sample. Here is a 100% reproduction of the problem.
Test1.txt used for the reproduction (you need a file sufficiently big for the error to occur)
Test1.txt
(Note that there is a correlation between this bug and the fact that it passes in the Cleanup then Read behaviour documented in the Dokan documentation and mentionned in #1016. I couldn't replicate it without having the Cleanup then Read behavior.)
The text was updated successfully, but these errors were encountered: