Plan9 has a network file system called 9p. Also really handy when trying to share storage between Host OS and virtualized guests in Qemu environment. Kinda like NFS, but less bloat.
Apparently bitcoind doesn’t like this file system, I assume it’s because of lacking file locking capabilities in leveldb on 9p… or something.
Anyways, would be awesome if debug.log would at least give an error message on why this is failing.
debug.log: 2014-02-07 10:54:46 Bitcoin version v0.8.6.0-g03a7d67-beta () 2014-02-07 10:54:46 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014 2014-02-07 10:54:46 Default data directory /var/lib/bitcoin/.bitcoin 2014-02-07 10:54:46 Using data directory /var/lib/bitcoin/.bitcoin 2014-02-07 10:54:46 Using at most 125 connections (1024 file descriptors available) 2014-02-07 10:54:46 Using 4 threads for script verification 2014-02-07 10:54:46 init message: Verifying wallet… 2014-02-07 10:54:46 dbenv.open LogDir=/var/lib/bitcoin/.bitcoin/database ErrorFile=/var/lib/bitcoin/.bitcoin/db.log 2014-02-07 10:54:46 Bound to 0.0.0.0:8333 2014-02-07 10:54:46 init message: Loading block index… 2014-02-07 10:54:46 Opening LevelDB in /var/lib/bitcoin/.bitcoin/blocks/index 2014-02-07 10:54:46 : Error opening block database. Do you want to rebuild the block database now? 2014-02-07 10:54:46 Shutdown : In progress… 2014-02-07 10:54:46 Flush(false) 2014-02-07 10:54:46 DBFlush(false) ended 1ms 2014-02-07 10:54:46 StopNode() 2014-02-07 10:54:47 Flushed 0 addresses to peers.dat 520ms 2014-02-07 10:54:47 Flush(true) 2014-02-07 10:54:47 DBFlush(true) ended 1ms 2014-02-07 10:54:47 Shutdown : done