OSError: [Errno 28] No space left on device

Open
#4,162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
blockchain

Research direction

Start with electrum/blockchain.py lines 233 and 241, following the call from electrum/network.py lines 540, 625, 966, and 984. Reproduce the disk-full failure and determine the expected behavior for header writes; done requires that behavior to be verified under the reported OSError condition.

Written by the indexing model from the issue text.

Description

Crash Report

This crash report was reported through the automatic crash reporting system 🤖

Traceback

  File "Electrum-3.1.1-py3.6.egg/electrum/util.py", line 792, in run_with_except_hook
  File "Electrum-3.1.1-py3.6.egg/electrum/network.py", line 984, in run
  File "Electrum-3.1.1-py3.6.egg/electrum/network.py", line 966, in wait_on_sockets
  File "Electrum-3.1.1-py3.6.egg/electrum/network.py", line 625, in process_responses
  File "Electrum-3.1.1-py3.6.egg/electrum/network.py", line 540, in process_response
  File "Electrum-3.1.1-py3.6.egg/electrum/network.py", line 1012, in on_notify_header
  File "Electrum-3.1.1-py3.6.egg/electrum/blockchain.py", line 241, in save_header
  File "Electrum-3.1.1-py3.6.egg/electrum/blockchain.py", line 233, in write

OSError: [Errno 28] No space left on device

Reporter

This issue was reported by 28 user(s):

Electrum Version Python Version Operating System Wallet Type Locale Stack
3.1.1 Darwin-17.5.0-x86_64-i386-64bit standard None ℹ
3.1.1 Windows-10-10.0.16299 standard ru_UA ℹ
3.1.1 Windows-10-10.0.14393-SP0 standard en_US ℹ
3.1.1 Windows-10-10.0.16299 standard en_US ℹ
3.1.2 Linux-4.16.1-300.fc28.x86_64-x86_64-with-fedora-28-Twenty_Eight standard en_AU ℹ
3.1.3 Darwin-14.5.0-x86_64-i386-64bit standard None ℹ
3.1.3 Windows-10-10.0.16299 standard ru_RU ℹ
3.1.3 Windows-10-10.0.16299 standard en_CA ℹ
3.1.3 Windows-10-10.0.16299 standard en_CA ℹ
3.1.3 Windows-10-10.0.16299 standard en_CA ℹ
3.2.0 Windows-10-10.0.17134 2fa ru_RU ℹ
3.2.0 Windows-10-10.0.17134 2fa ru_RU ℹ
3.1.3 Windows-7-6.1.7601-SP1 standard ru_RU ℹ
3.1.3 Windows-7-6.1.7601-SP1 standard ru_RU ℹ
3.2.2 Windows-10-10.0.17134 standard de_DE ℹ
3.1.1 Windows-10-10.0.17134 standard de_DE ℹ
3.2.2 Windows-7-6.1.7601-SP1 standard en_US ℹ
3.2.3 3.6.4 (default, Mar 1 2018, 10:42:21) [GCC 5.3 20151204] Android 7.0 on Verizon j7popltevzw (NRD90M.J727VVRS2ARC1) unknown ? ℹ
3.2.3 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609] Linux-4.15.0-32-generic-x86_64-with-LinuxMint-18.2-sonya imported en_PH ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17134 standard en_US ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17134 standard en_US ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17134 standard ru_UA ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17134 standard ru_UA ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17134 standard ru_UA ℹ
3.2.3 3.6.6 (default, Jun 27 2018, 14:44:17) [GCC 8.1.0] Linux-4.17.0-kali1-amd64-x86_64-with-Kali-kali-rolling-kali-rolling standard en_US ℹ
3.2.3 3.6.6 (default, Jun 27 2018, 14:44:17) [GCC 8.1.0] Linux-4.17.0-kali1-amd64-x86_64-with-Kali-kali-rolling-kali-rolling standard en_US ℹ
3.2.3 3.6.4 (default, Feb 28 2018, 03:24:19) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)] Darwin-17.7.0-x86_64-i386-64bit standard ? ℹ
3.2.3 3.6.6 (v3.6.6:4cf1f54eb7, Jun 27 2018, 02:47:15) [MSC v.1900 32 bit (Intel)] Windows-10-10.0.17763 standard nl_NL ℹ

Additional Information

Electrum was idle in the background.

It was idling in the background, I've not updated in a while.

Dominant language
Python
Stars
8.6k
Forks
3.5k
Avg merge
2d 8h
Merged PRs (30d)
61

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spesmilo/electrum

All issues in spesmilo/electrum

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.