Author

Topic: bitcoin data directory on Synology smb share (Read 84 times)

legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
October 12, 2023, 07:35:10 AM
#4
Also, SMB connections tend to close unexpectedly. And I have tried to get samba shares to automount during boot but it was only after I mounted the shares manually that I was able to access the files inside. Of course, part of it might have been because of my use of Kerberos (because it is, you know, a network share), but even if that concern is excluded, SMB read and write speeds are horribly slow, much slower than HDD drives.
newbie
Activity: 2
Merit: 1
@achow11:
Thanks for your advise.
 I hoped I could use my diskarray and their automatic backup functions to secure the data instead of separate discs.  Sad

regards
uwe
staff
Activity: 3458
Merit: 6793
Just writing some code
It's generally inadvisable to use a network share for your Bitcoin Core data directory. Bitcoin Core does a lot of disk I/O and it depends on files existing on disk where it expects them to be and at all times. Since networks are not always reliable, any hitch in the network can cause Bitcoin Core to crash unexpectedly and possibly corrupt the data in its data directory. You just shouldn't try doing that.
newbie
Activity: 2
Merit: 1
Bitcoin mac version : v25.0.0  
mac os version :  14.0 (23A344)

I tried to set the data directory on a Synology DSM running Version 7.2 on Synology.

on a fresh directory bitcoin program creates the the blocks dir, the settings.json file and the .lock file on the share. It than stops with the following error message:
Cannot obtain a lock on data directory /Volumes/btc. Bitcoin Core is probably already running.

no additional bitcoin process is running on mac. I tried all possible smb protocol versions on the Synology, no success. all access rights are checked. the user has all rights to write, read and all administration rights.

any suggestions ?

one additional info:
Instead of the mac version I tried the windows version with W11 in a VM on macOS and the same share on the Synology. It works with no errors till now !!

Jump to: