I'm trying to understand an error I see often in my renter.log:
uploadchunk.go:526: falling back to remote download for repair: fetch from local file /.../.../....rar failed: [local file failed the integrity check; physical data integrity check has failed]
(The file is still present on that path and is unchanged.)
The file was added via siasync and I copied the file into the folder via samba from a windows pc where siasync is watching for changes. My guess is that the file is added to sia before the transfer via samba is finished and thus sia uploaded a 'wrong' state of the file.
Restarting siasync in this situation and rehashing the file does not trigger a reupload of the file, only a renaming of the file seems to solve the problem (with a complete reuploading of the file).
Maybe this is a problem with sia and not siasync.
I am using sia 1.4.7-master (Git rev 000eccb45) on a rasperry pi 4.
I'm trying to understand an error I see often in my renter.log:
uploadchunk.go:526: falling back to remote download for repair: fetch from local file /.../.../....rar failed: [local file failed the integrity check; physical data integrity check has failed]
(The file is still present on that path and is unchanged.)
The file was added via siasync and I copied the file into the folder via samba from a windows pc where siasync is watching for changes. My guess is that the file is added to sia before the transfer via samba is finished and thus sia uploaded a 'wrong' state of the file.
Restarting siasync in this situation and rehashing the file does not trigger a reupload of the file, only a renaming of the file seems to solve the problem (with a complete reuploading of the file).
Maybe this is a problem with sia and not siasync. I am using sia 1.4.7-master (Git rev 000eccb45) on a rasperry pi 4.