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

Windows Explorer shows C: drive capacity for any vault #80

Closed
tobihagemann opened this Issue Sep 2, 2015 · 8 comments

Comments

Projects
None yet
8 participants
@tobihagemann
Copy link
Member

tobihagemann commented Sep 2, 2015

No matter where the vault is actually located, Windows Explorer always shows the C: drive capacity for any vault. Discussed on Reddit. Seems to be a Windows issue, has to be fixed by Microsoft.

@mholtzscher

This comment has been minimized.

Copy link

mholtzscher commented Sep 3, 2015

On my PC(win 8.1 64bit) my vault said it had a max size of 237 gigabyte with free space of 104g. If I tried to copy in folder larger than the remaining free space then I got file too large errors. I was able to get around this by using TeraCopy and I have successfully put in over 300gigs of files into my drive.

@sergeevabc

This comment has been minimized.

Copy link

sergeevabc commented Nov 8, 2017

It blows my mind that Cryptomator was released for production use with such a discrepancy.
Obviously, a wrong choice of subroutine, which is WebDAV, let alone large files issue.

@markuskreusch

This comment has been minimized.

Copy link
Contributor

markuskreusch commented Nov 9, 2017

There are several reasons that WebDAV has been choosen as protocol:

  • WebDAV can be used on more or less any system without specific adaptions. This reduces the complexity of the overall product. This reduces the efforts for changes and maintenance, which is vital for open source products.
  • WebDAV shares are mountable without a deep system integration. So using the Software without Administrative rights is possible.

I understand, that the problems seem pretty bad if you wan't to use large files or have small space on drice C available. However this does not affect that many users. The usage of an external WebDAV client is possible to circumvent this limitations. We are working on an improvement (see #207 / #252) but due to the system specific nature of a direct file system integration this process takes some time.

@DougBeney

This comment has been minimized.

Copy link

DougBeney commented Nov 9, 2017

Might be a silly question, but what would be the disadvantages of the way Veracrypt works, where it actually mounts a virtual drive to your system?

@tobihagemann

This comment has been minimized.

Copy link
Member

tobihagemann commented Nov 9, 2017

It's not a silly question at all. The answer is quite simple: There is no disadvantage.

The current situation is just how Cryptomator has evolved as a project. It started with WebDAV because it was the fastest and easiest way to offer a virtual drive on all operating systems. And now we're working on a FUSE/Dokany integration, which takes significantly more time to implement.

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jul 12, 2018

Good news, everyone! We've released version 1.4.0-beta2, which introduces Dokany support. You now have the choice between Dokany and WebDAV based virtual hard drives.

Please retest this issue with Dokany enabled.

@infeo

This comment has been minimized.

Copy link
Member

infeo commented Jul 17, 2018

With dokany it works. and even better, it updates its status when doing something somewhere else on the same partition :D

@loungebob

This comment has been minimized.

Copy link

loungebob commented Oct 1, 2018

I must be doing something wrong. Even beta 2 does not work for me. Dokany creates a virtual, inaccessible floppy drive on A: and Fuse the same virtual drive as Web DAV with the same limitations (space of C: drive). How do I get rid of the free space limitation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment