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.

Sign up for GitHub

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

Jump to bottom

[Volume usage increment] Upgrading Erigon from v255.1 -> v2.57.0 causes a disk usage increment of almost 100gb #9294

Closed
luarx opened this issue Jan 24, 2024 · 1 comment
Closed

[Volume usage increment] Upgrading Erigon from v255.1 -> v2.57.0 causes a disk usage increment of almost 100gb #9294

luarx opened this issue Jan 24, 2024 · 1 comment

Comments

@luarx
Copy link

luarx commented Jan 24, 2024

System information

Erigon version: v2.57.0

OS & Version: Docker

Consensus Layer: v4.4.1

Chain/Network: Sepolia

Expected behaviour

Disk usage should be more or less stable

Actual behaviour

There is an increment of 100gb aprox. in Sepolia (didn't try on mainnet yet)

Steps to reproduce the behaviour

Upgrade from v2.55.1 -> v2.57.0

image
@AskAlexSharov AskAlexSharov mentioned this issue Jan 24, 2024
Merged
AskAlexSharov added a commit that referenced this issue Jan 24, 2024
@AskAlexSharov
downloader: prohibit_new_downloads.lock check missed download .torren…
56db532 
…t from WebSeed (#9295)

moved `.lock` file handling inside `TorrentFiles` class - which is
available everywhere and guarded by mutex.

fixing: #9294
yperbasis pushed a commit that referenced this issue Jan 24, 2024
@AskAlexSharov @yperbasis
downloader: prohibit_new_downloads.lock check missed download .torren…
fbf1850 
…t from WebSeed (#9295)

moved `.lock` file handling inside `TorrentFiles` class - which is
available everywhere and guarded by mutex.

fixing: #9294
@yperbasis
Copy link
Member

Fixed by PR #9295 and in v2.57.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@luarx @yperbasis