Geth starts processig entire chain from beginning after out of disk error

[gsj5]

System information

Version: 1.5.0-unstable
Protocol Versions: [63 62 61]
Network Id: 1
Go Version: go1.5.1
OS: Linux ip-172-31-11-69 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Expected behaviour

geth continues importing blocks from where it left off from the last run, when it ran out of disk space

Actual behaviour

geth starts syncing from block 0!!

Steps to reproduce the behaviour

I am having hell of time trying to sync the chain for past 10 days now. This is my 7th attempt and unfortunately this last one failed due to out of disk space. Running geth again starts sync process from beginning. Think I am ready to give up...

I0511 00:49:08.695942 core/blockchain.go:959] imported 256 block(s) (0 queued 0 ignored) including 715 txs in 25.057401611s. #1339489 [e92ec212 / b31ebbb9]
I0511 00:49:37.852357 core/blockchain.go:959] imported 256 block(s) (0 queued 0 ignored) including 1585 txs in 29.155350085s. #1339745 [0dc5412d / 574e6c49]
I0511 00:50:14.623508 core/blockchain.go:959] imported 256 block(s) (0 queued 0 ignored) including 1830 txs in 36.770056141s. #1340001 [e68897b5 / fc7c85f8]
F0511 00:50:33.839782 core/database_util.go:296] failed to store block body into database: write /eth/.ethereum/chaindata/393008.log: no space left on device

After restart:

I0511 02:40:29.876816 ethdb/database.go:82] Alloted 128MB cache and 1024 file handles to /eth/.ethereum/chaindata
I0511 02:40:30.171744 ethdb/database.go:169] closed db:/eth/.ethereum/chaindata
I0511 02:40:30.174414 ethdb/database.go:82] Alloted 128MB cache and 1024 file handles to /eth/.ethereum/chaindata
I0511 02:40:30.250248 ethdb/database.go:82] Alloted 16MB cache and 16 file handles to /eth/.ethereum/dapp
I0511 02:40:30.253422 eth/backend.go:170] Protocol Versions: [63 62 61], Network Id: 1
I0511 02:40:30.253599 eth/backend.go:199] Blockchain DB Version: 3
I0511 02:40:30.256016 core/blockchain.go:206] Last header: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.256033 core/blockchain.go:207] Last block: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.256038 core/blockchain.go:208] Fast block: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.256170 core/blockchain.go:206] Last header: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.256178 core/blockchain.go:207] Last block: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.256183 core/blockchain.go:208] Fast block: #0 [d4e56740…] TD=17179869184
I0511 02:40:30.259291 p2p/server.go:311] Starting Server
I0511 02:40:31.990628 p2p/discover/udp.go:217] Listening, enode://bd85c1f8ecb475f44505bda5c49a7887f7f72a060235a4df7bc5a841fc1a701edafe725a9b2cfb1f697554ddd0f27eb4acb4e265d68b481fda01cf502e0249ee
@[::]:30303
I0511 02:40:31.993094 p2p/server.go:554] Listening on [::]:30303
I0511 02:40:31.993349 node/node.go:298] IPC endpoint opened: /eth/.ethereum/geth.ipc
I0511 02:40:41.993498 eth/downloader/downloader.go:295] Block synchronisation started
I0511 02:40:46.419586 core/blockchain.go:959] imported 0 block(s) (0 queued 2 ignored) including 0 txs in 1.966749297s. #2 [88e96d45 / b495a1d7]
I0511 02:40:46.586908 core/blockchain.go:959] imported 0 block(s) (0 queued 90 ignored) including 0 txs in 165.968641ms. #92 [3d612266 / c86dcbd8]
I0511 02:41:01.220303 core/blockchain.go:959] imported 0 block(s) (0 queued 256 ignored) including 0 txs in 621.026283ms. #348 [fd07e36c / 0b2975c0]
I0511 02:41:01.926539 core/blockchain.go:959] imported 0 block(s) (0 queued 256 ignored) including 0 txs in 705.363727ms. #604 [44952440 / 5e9156c1]

[obscuren]

The entire block chain is about 15gb at present and simply requires this amount of data. Going out of data mid write will cause database corruption.

Have you considered using the --fast sync? This won't require more than 3gb of data. You'll need to delete your chaindata folder before enabling sync. We're currently working on pruning that will allow you to delete irrelevant data.

[sheraz658]

Please help on below issue:
geth --testnet
I1025 10:12:44.731831 ethdb/database.go:83] Alloted 128MB cache and 1024 file handles to /home/ubuntu/.ethereum/testnet/chaindata
Fatal: Could not open database: write /home/ubuntu/.ethereum/testnet/chaindata/111615.ldb: no space left on device

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.