-
Notifications
You must be signed in to change notification settings - Fork 35.6k
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
Unable to load the databases when mounted over a samba file share #7981
Comments
This looks like an open bug in leveldb: google/leveldb#281 |
Most network based filesystems are currently not supported by leveldb/bitcoind. |
Please consider the block database is huge and growing, so the need of storing it on a NAS could become more popular in future. |
I partial agree with @gtozzi. I think the UTXO database should not be on a NAS (or lets say high latency & slow speed persistence store) but there could be reasons to keep the block files on a NAS (especially age >144 blocks). |
You could try my I agree with @jonasschnelli though - what I'd suggest doing is to store the databases ($DATADIR/blocks/index) and ($DATADIR/chainstate) locally on a fast disk, and the block files on a (slower) remote device. There is no (direct) option to do this at the moment, but it can be accomplished by symbolic linking. |
I use this script to move old
|
When the data directory is mounted on a samba file share using cifs, I am unable to load the databases. It always starts with an error message asking to reindex the databases.
This is the error from the debug.log
2016-04-27 20:36:22 init message: Loading block index... 2016-04-27 20:36:22 Opening LevelDB in /home/achow101/.bitcoin/blocks/index 2016-04-27 20:36:24 IO error: /home/achow101/.bitcoin/blocks/index: Invalid argument 2016-04-27 20:36:28 Aborted block database rebuild. Exiting.
I think it has to do with how cifs does file sharing, but I'm not sure.
Other people have also seen this problem: https://bitcointalk.org/index.php?topic=1454844.msg14707662#msg14707662
The text was updated successfully, but these errors were encountered: