Merge #12653: Allow to optional specify the directory for the blocks storage
a192636-blocksdir: keep blockindex leveldb database in datadir (Jonas Schnelli)f38e4fdQA: Add -blocksdir test (Jonas Schnelli)386a6b6Allow to optional specify the directory for the blocks storage (Jonas Schnelli) Pull request description: Since the actual block files taking up more and more space, it may be desirable to have them stored in a different location then the data directory (use case: SSD for chainstate, etc., HD for blocks). This PR adds a `-blocksdir` option that allows one to keep the blockfiles and the blockindex external from the data directory (instead of creating symlinks). I fist had an option to keep the blockindex within the datadir, but seems to make no sense since accessing the index will (always) lead to access (r/w) the block files. Tree-SHA512: f8b9e1a681679eac25076dc30e45e6e12d4b2d9ac4be907cbea928a75af081dbcb0f1dd3e97169ab975f73d0bd15824c00c2a34638f3b284b39017171fce2409
This commit is contained in:
+1
-1
@@ -623,7 +623,7 @@ int main(int argc, char *argv[])
|
||||
if (!Intro::pickDataDirectory())
|
||||
return EXIT_SUCCESS;
|
||||
|
||||
/// 6. Determine availability of data directory and parse bitcoin.conf
|
||||
/// 6. Determine availability of data and blocks directory and parse bitcoin.conf
|
||||
/// - Do not call GetDataDir(true) before this step finishes
|
||||
if (!fs::is_directory(GetDataDir(false)))
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user