Skip to content
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

Saving the blockchain to network storage (NAS) does not work correctly #1302

Open
vampyren opened this issue Aug 8, 2023 · 0 comments
Open

Comments

@vampyren
Copy link

vampyren commented Aug 8, 2023

Describe the issue

When using network drive to save the blockchain wallet does some nasty stuff which sort of don't make any sense. I believe
the code underneath does not handle network drive in a correct way.
Almost half the files are stored correct and other half not so.

Local setup

Windows 11 x64.
Firo Core version v0.14.12.1-gc7e3ef0e6 (64-bit)

Any extra information that might be useful in the debugging process.

path
firo_folders

As seen from the images i wanted to have my data folder at:
\myVault\Temp\Blockchain\firo

But as the other image shows files under \myVault\Temp\Blockchain\firo\blocks are stored correctly
while files under these folders are still stored locally under C:\Util\Crypto\firo-0.14.12.1\bin
\myVault\Temp\Blockchain\firo\blocks\index
\myVault\Temp\Blockchain\firo\blocks
\myVault\Temp\Blockchain\firo\chainstate
\myVault\Temp\Blockchain\firo\evodb
\myVault\Temp\Blockchain\firo\llmq

This does not make any sense! To me this is a coding error in how path's are handled in the wallet. Also as a proof for my own theory When i tried to move the data dir to the default location: \AppData\Roaming\firo and started with a fresh wallet (clean registry) it had to re-download the whole chain again since allot of files were missing due to the above mentioned issue. The whole data is not saved correctly when using network folder!

And this is nothing special. I have BTC, LTC, Dash, Pivx all using network storage with no issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant