-
Notifications
You must be signed in to change notification settings - Fork 186
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
Not enough space on connected USB drive when recovering (Windows Version, ophotorec) #99
Comments
https://github.com/cgsecurity/testdisk_documentation/blob/master/photorec.rst now contains I don't plan to implement customizable file size limits. What do you suggest to replace "There is not enough space left! Please free disk space and/or choose another destination" ? |
Thanks for the prompt reply Christophe, let me start by saying I really appreciate the software and was already able to rescue a lot of data! As more and more less tech-savvy people start using tools like this, and as external USB HDD are often pre-formatted FAT this is a real issue and was even confusing to me. If I had used an (internal) drive with ext4 on Linux I wouldn't have even noticed. I am not a C programmer (html, js, php mostly), so excuse for only giving suggestions and not offering a PR
|
@cgsecurity I just retried the steps - this time with an NTFS formatted 65GB drive. |
@leotulipan were you able to find a solution? I and using a NTFS HDD and am getting the same message :/ |
Latest pre-compiled Win x64 Version-
Restoring to a standard (FAT32) External empty 512GB HDD from the local 2568GB SSD in Win10
I get "There is not enough space left! Please free disk space and/or choose another destination"
which is related to PSTATUS_ENOSPC switch/case here
https://github.com/cgsecurity/testdisk/blob/master/src/qphotorec.cpp
https://github.com/cgsecurity/testdisk/blame/master/src/phrecn.c
It might be related to the old open issue #9
as I only selected doc, pdf and zip as the file options I am guessing some >4GB zip/tmp file is being written and I cannot skip this part.
The text was updated successfully, but these errors were encountered: