This repository was archived by the owner on Nov 6, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Parity Taking Up All My C: Drive. HELP! #7419
Labels
Milestone
Comments
Please upgrade to 1.7.11-stable or 1.8.5-beta and reset your database with:
|
Duplicate of #6280 |
Where can I preform this upgrade? |
Wait until your client is fully synchronized. Your issue will be fixed in 1.8.6 coming up this week. |
Ok, I did a parity kill and my chain is resyncing now. I was also told to do this cmd: parity.exe --min-peers 100 --max-peers 500 --log-file=parity.log is that ok? |
looks good. |
Will I keep having to delete my parity chains every few weeks though to keep my C drive from filling up again? |
No. Not once we released 1.8.6 :) Stay tuned :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Before filing a new issue, please provide the following information.
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
Hi,
My C drive says it is full. Under C:\User\myname\AppData\Parity\Ethereum\chains\ethereum\db
I see tons and tons of gigabyte files here. Can I delete all these? I there a simple way to copy and paste all these chains to my D Drive? What is the most efficient/safe way to fix this problem?
Thank you in advance.
The text was updated successfully, but these errors were encountered: