Skip to content
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

p7zip error 2 on compressing big files over 100mb #361

Closed
v6 opened this issue Jan 30, 2019 · 5 comments
Closed

p7zip error 2 on compressing big files over 100mb #361

v6 opened this issue Jan 30, 2019 · 5 comments
Assignees
Milestone

Comments

@v6
Copy link

v6 commented Jan 30, 2019

// , #18

@v6
Copy link
Author

v6 commented Jan 30, 2019

// , Doesn't matter whether I use AES-256 or not.

@aonez aonez self-assigned this Jan 30, 2019
@aonez aonez added this to the Look at milestone Jan 30, 2019
@aonez
Copy link
Owner

aonez commented Jan 30, 2019

Thanks for creating another ticket. #18 has to do with ZIP files bigger than 4GB (64bit), specifically created on Mac OS X with the bundled compressor.

Can you provide more information? Does it occur on every file? What formats? Can you share one?

@v6
Copy link
Author

v6 commented Jan 30, 2019 via email

@aonez aonez changed the title p7zip error 2 on big files over 100mb p7zip error 2 on compressing big files over 100mb Jan 30, 2019
@aonez
Copy link
Owner

aonez commented Jan 30, 2019

@v6 you can enable the verbose mode on Keka and take a look at the Console.app:

defaults write com.aone.keka DevLog -bool true
defaults write com.aone.keka DevLogReader -bool true

Remember to disable those (setting them to false) after. Those extra messages can affect the performance of Keka.

It does only happens with files over 100MB? And happens with all files over 100MB or just specific ones?

@no-response
Copy link

no-response bot commented Feb 28, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Feb 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants