Cannot upload files larger than 10/20 Gigabytes

[GoogleCodeExporter]

If you try to upload any files or folders larger than 10/20 Gigabytes I get
an error that there is not enough space on the available drive (which is
not true). The "Dokan" drive though does say "10 GB free of 20 GB" (my
drive is 500 GB). Is there a way to either set the ACTUAL space or possibly
more space than the actual so I do not get this error?

Thanks,
Will

Original issue reported on code.google.com by will.robles@gmail.com on 14 Oct 2008 at 7:26

[GoogleCodeExporter]

Yes,

This is an important issue. I have a similiar problem. A quick work-around 
would be
to change the (constant) amount of free diskspace reported by the SSHFS/Dokan 
driver
to something ridiculously big - like 1 terabyte.

I can't install a program that requires 15 GB of free disk space via SSHFS 
because it
checks the avaiable diskspace and says there is not enough space available on 
the device.

Original comment by kako...@gmail.com on 13 Jun 2009 at 2:10

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

as remarked in http://code.google.com/p/dokan/issues/detail?id=82 (bug 82).  
this could be "patched" by user in

You can play with the default space settings of the drive in the source code 
amend 
lines 32 / 34 in dokan/volume.c 

http://code.google.com/p/dokan/source/browse/trunk/dokan/volume.c

Original comment by ddeme...@gmail.com on 11 Sep 2009 at 9:31

[GoogleCodeExporter]

Having the same issue using DokanSSHFS to transfer a large file (11GB.)  Not 
really 
sure what todo w/ the Volume.c file so... might as well use WinSCP for the 
large files.

Original comment by djpeter...@gmail.com on 2 May 2010 at 9:42

[GoogleCodeExporter]

I concur; for me the "20GB" drive size problem is fatal. I realize determining 
actual 
size will be difficult, but 20GB is a FILE size today, not a partition or disk 
size. 

Though it would be a crock, a configurable size field in the connect-server 
dialog 
box would probably be sufficient.

Until it's fixed, dokan is useless to me.

-- tomj

Original comment by tomj....@gmail.com on 6 May 2010 at 1:42

[GoogleCodeExporter]

As a workaround, you can try using SuperCopier.  It allowed me to force the 
transfer to 
continue anyway.  Unfortunately won't help for installing programs there.

Original comment by HTL2...@gmail.com on 20 May 2010 at 4:31

[GoogleCodeExporter]

Looks like fix should be done in dokan_sshfs/DokanSSHFS/DokanOperations.cs:966 
where you can find actual limits for DokanSSHFS application (10 GB available 
out of 20 GB). Limits from dokan/volume.c will be used only if you have a bug 
in your application (in this case - DokanSSHFS).
Preferably fix should detect real available size, but not guess it.

Original comment by the....@gmail.com on 4 Jun 2011 at 11:30

[GoogleCodeExporter]

Has anyone compiled a work around for this yet? I just need basic Dokan 0.6 
with the ability to handle large files. I really don't think it would be right 
to pay annually to Boxcryptor...would rather fork my own software then pay 
annually to access my own data.

Original comment by hacked2...@gmail.com on 27 Aug 2014 at 12:32