-
Notifications
You must be signed in to change notification settings - Fork 655
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
Allocation unit size as option #164
Comments
Hi @marinkobabic , I am currently looking for this ticket to integrate it in the 1.0.0. I was thinking that Line 104 in e370ff8
Line 232 in e370ff8
For me the Do you think the values should be updated ? for now it don't seems to create an issue 😄 |
See https://github.com/dokan-dev/dokany/compare/ClusterSizeOption?expand=1 with the current changes |
@Liryna You are right, but the information is displayed in explorer is the volume size which is updated by the user. Makes not a big difference if you update the disk information or not. Usually a volume can be created over one or more disks. |
Thank you for your input @marinkobabic ! This has been done and can be tested with mirror option by creating a file with 1 byte and observing the real file size changing depending of the value used. |
We should be able to set the allocation unit size of the device as a DokanOption or during the Mount.
DOKAN_ALLOCATION_UNIT_SIZE
DOKAN_SECTOR_SIZE
The value should also be checked to fit the windows FAT/NTFS value:
https://support.microsoft.com/en-us/kb/140365
The text was updated successfully, but these errors were encountered: