Bitcoin Forum
September 23, 2018, 11:06:35 PM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bitcoint-Qt and -wallet parameter : Can't specify a different folder ?  (Read 227 times)
BobLawblaw
Legendary
*
Offline Offline

Activity: 1036
Merit: 1501


Bitcointalks Most Fabulously Gay Black Power-Top


View Profile
December 03, 2017, 12:39:23 PM
 #1

   -wallet=<file>   Specify wallet file (within data directory) (default: wallet.dat)

Any idea why this is ?

I would like to use my main laptop SSD to house the wallet.dat, and use an external USB drive to house the blockchain and other related data, and Bitcoin-Qt was having none of it.

Any idea what the rationale is for not allowing a different path to your wallet.dat ?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1537743995
Hero Member
*
Offline Offline

Posts: 1537743995

View Profile Personal Message (Offline)

Ignore
1537743995
Reply with quote  #2

1537743995
Report to moderator
1537743995
Hero Member
*
Offline Offline

Posts: 1537743995

View Profile Personal Message (Offline)

Ignore
1537743995
Reply with quote  #2

1537743995
Report to moderator
neurotypical
Hero Member
*****
Offline Offline

Activity: 672
Merit: 500


View Profile
December 03, 2017, 11:46:18 PM
 #2

   -wallet=<file>   Specify wallet file (within data directory) (default: wallet.dat)

Any idea why this is ?

I would like to use my main laptop SSD to house the wallet.dat, and use an external USB drive to house the blockchain and other related data, and Bitcoin-Qt was having none of it.

Any idea what the rationale is for not allowing a different path to your wallet.dat ?

As far as I've read is not really a good idea to split contents of the bitcoin folder, it's better to have it all on the same place. I saw people asking if they could split the chainstate files to make it faster by putting them in an SSD and they got told that its not a good idea..

But if you want to change the data folder:

Quote
"C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe" -datadir=d:\BitcoinData

This will put the entire data folder in another hard disk called D: in a folder called "BitcoinDat" for example.

achow101
Moderator
Legendary
*
expert
Offline Offline

Activity: 1526
Merit: 1650


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
December 04, 2017, 04:18:13 AM
 #3

Any idea what the rationale is for not allowing a different path to your wallet.dat ?
The wallet.dat file is a database. When the database is opened, other temporary files will also be opened in a given location. That location is usually the Bitcoin Core datadir. However having the temporary database files and the wallet database itself located in two different places may cause issues, especially with unclean shutdowns and moving wallet files. Thus to avoid issues with that, wallets must be in the same directory as the temporary database files, which is the datadir.

This is also why symlinks have also been disallowed. That they were allowed in the past was a bug.

BobLawblaw
Legendary
*
Offline Offline

Activity: 1036
Merit: 1501


Bitcointalks Most Fabulously Gay Black Power-Top


View Profile
December 04, 2017, 05:15:19 AM
 #4

However having the temporary database files and the wallet database itself located in two different places may cause issues, especially with unclean shutdowns and moving wallet files. Thus to avoid issues with that, wallets must be in the same directory as the temporary database files, which is the datadir.
This is also why symlinks have also been disallowed. That they were allowed in the past was a bug.

Fair enough. Thank you for clearing that up.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!