# Write-hashtbl hashstore: collision detected **URL:** \ **Category:** troubleshooting\ **Tags:** error-codes, hashstore\ **Created:** [January 9, 2026, 12:44pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359 "2026-01-09T12:44:35Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\ **Post date:** [January 9, 2026, 12:44pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/1 "2026-01-09T12:44:35Z")
Hi, I’m using write-hashtbl and run into a new situation: ```auto hashstore: put:{key:1b1bbd32f020502e52e839717e13a486ae0b9f6eff7c2f25001bf1df606bc12e offset:1073162112 log:116 length:2319872 created:20450 (2025-12-28) expires:0 (1970-01-01) trash:false} != exist:{key:1b1bbd32f020502e52e839717e13a486ae0b9f6eff7c2f25001bf1df606bc12e offset:95672576 log:100 length:2319872 created:20450 (2025-12-28) expires:0 (1970-01-01) trash:false}: hashstore: collision detected storj.io/storj/storagenode/hashstore.(*HashTbl).insertLocked:384 storj.io/storj/storagenode/hashstore.(*HashTblConstructor).Append:525 main.(*cmdRoot).Execute.func2:110 main.(*cmdRoot).iterateRecords:201 main.(*cmdRoot).Execute:109 github.com/zeebo/clingy.(*Environment).dispatchDesc:129 github.com/zeebo/clingy.Environment.Run:41 main.main:29 runtime.main:283 ``` How do I fix this? ---
**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\ **Post date:** [January 9, 2026, 3:20pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/2 "2026-01-09T15:20:11Z")
Seem like I just need to delete log 64 (decimal 100) and log 74 (decimal 116) it will work again. ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [January 9, 2026, 5:28pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/3 "2026-01-09T17:28:48Z")
This is not a solution. It’s curing headache with a guillotine. The solution would be to find a root cause and fix that, not kill the patient. ---
**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\ **Post date:** [January 14, 2026, 8:30am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/4 "2026-01-14T08:30:04Z")
This is not a dangerous error. Old piecestore silently ignored double uploads, hashstore doesn’t. Should be very rare (for example: piece is deleted, and repair tries to re-upload with the same ID). _never delete log files_ because this. That will delete healthy pieces and will cause disqualification. ---
**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\ **Post date:** [January 14, 2026, 11:59am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/5 "2026-01-14T11:59:42Z")
It look like a dangerous error, effectively stop node from being online.. how do we `properly` fix that? P/s: since I run into this issue first, may I provide node id to prevent my node from being disqualified here? ---
**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\ **Post date:** [January 23, 2026, 8:23pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/7 "2026-01-23T20:23:22Z")
> [@kocoten1992](#): > > It look like a dangerous error, effectively stop node from being online.. how do we `properly` fix that? There should be some other error. Collision itself doesn’t prevent node from being online. Actually, I just changed the level from ERROR to WARN. ---
**Author:** ![kocoten1992](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kocoten1992/32/7819_2.png) [@kocoten1992](https://forum.storj.io/u/kocoten1992)\ **Post date:** [January 24, 2026, 12:12am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/8 "2026-01-24T00:12:14Z")
I don’t recall any other errors. The logs show that it was stuck in a restart loop with that error. Once I fixed it using `write-hashtbl`, it went back to normal 🙂 ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [January 30, 2026, 5:04am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/9 "2026-01-30T05:04:51Z")
actually it is Unrecoverable error. I got it also and node wont start. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [January 30, 2026, 6:24am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/10 "2026-01-30T06:24:49Z")
It should be fixed with these changes: > [@Unrecoverable error](https://forum.storj.io/t/unrecoverable-error/31411/2): > > Here are proposed changes: > [https://review.dev.storj.tools/c/storj/storj/+/20196](https://review.dev.storj.tools/c/storj/storj/+/20196) storagenode/hashstore: skip log file check bool > [https://review.dev.storj.tools/c/storj/storj/+/20197](https://review.dev.storj.tools/c/storj/storj/+/20197) storagenode/hashstore: log hint info > [https://review.dev.storj.tools/c/storj/storj/+/20198](https://review.dev.storj.tools/c/storj/storj/+/20198) storagenode/hashstore: ignore collisions during fsck ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [January 30, 2026, 6:32am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/11 "2026-01-30T06:32:43Z")
if updates will go like now, my nodes will be DQ before this updates see the light. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [January 30, 2026, 7:01am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/12 "2026-01-30T07:01:20Z")
The team is aware of the problem, as you can see by these changes, so they should be included to the new version. I also think that we back on track, so it should be updated before the node will be disqualified for downtime. ---
**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\ **Post date:** [January 30, 2026, 10:21am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/13 "2026-01-30T10:21:05Z")
Please note, that – in general – we recommend to use the version which is published by [https://version.storj.io/](https://version.storj.io/), because that’s the tested one which passed all QA test, and also tested in select network for a certain time period. Currently it (1.142.7) is an older one, because still we are testing new hashstore versions in select. We are grateful, if somebody is always testing the latest version, but it’s always a higher risk. * * * After this generic disclaimer, let’s be more specific. v1.146.6 is just published with all known hashstore fixes. Most of the problems were introduced by v1.146.5 (the first release with fsck support), so regular users can safely wait until do roll out. For all the pioneers who are willing to help with testing: Please don’t use v1.146.5, only v1.146.6 from the v1.146. I just deployed it to one select node, so I am also just at the beginning of the testing (but most of the commits are already tested in select, just not the fixes) (@Vadim: it should also include fix for different space calculation after restart on windows) ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [January 30, 2026, 10:44am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/14 "2026-01-30T10:44:17Z")
Thank you i will try, generally today I use 1.146.5 everywhere, and it working fine. ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [January 30, 2026, 10:59am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/15 "2026-01-30T10:59:24Z")
thank you for update. i have 2 nodes that have error, one node service gone live. but dashboard not loading and log show this error 2026-01-30T12:53:14+02:00 ERROR contact:amnesty failed to get satellite URL for amnesty report {“satellite”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “piece\_count”: 2, “error”: “trust: satellite is untrusted”, “errorVerbose”: “trust: satellite is untrusted\n\tstorj.io/storj/storagenode/trust.init:29\n\truntime.doInit1:7670\n\truntime.doInit:7637\n\truntime.main:256”} how one of the main satellites can be untrusted? second node has also hashstore table problem, but i cant rebuild it, because write-hashtbl show same collision error and wont rebild it. ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [February 13, 2026, 6:07am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/16 "2026-02-13T06:07:11Z")
A post was merged into an existing topic: [Recovering hashstore on Windows](https://forum.storj.io/t/recovering-hashstore-on-windows/31219/44) ---
**Author:** ![vladro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/vladro/32/1129_2.png) [@vladro](https://forum.storj.io/u/vladro)\ **Post date:** [February 11, 2026, 10:45pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/17 "2026-02-11T22:45:12Z")
my result is: (node is not running) hashstore: put:{key:9db4ea9c83d49db0e2fd248a50d91771a6df4febf88f20de2ee3cec1da4ee0dd offset:153484096 log:292 length:2319872 created:20475 (2026-01-22) expires:20496 (2026-02-12) trash:true} != exist:{key:9db4ea9c83d49db0e2fd248a50d91771a6df4febf88f20de2ee3cec1da4ee0dd offset:989348416 log:265 length:2319872 created:20475 (2026-01-22) expires:0 (1970-01-01) trash:false}: hashstore: collision detected [storj.io/storj/storagenode/hashstore.(\*HashTbl).insertLocked:411](http://storj.io/storj/storagenode/hashstore.(*HashTbl).insertLocked:411) [storj.io/storj/storagenode/hashstore.(\*HashTblConstructor).Append:552](http://storj.io/storj/storagenode/hashstore.(*HashTblConstructor).Append:552) main.(\*cmdRoot).Execute.func2:111 main.(\*cmdRoot).iterateRecords:211 main.(\*cmdRoot).Execute:110 [github.com/zeebo/clingy.(\*Environment).dispatchDesc:129](http://github.com/zeebo/clingy.(*Environment).dispatchDesc:129) [github.com/zeebo/clingy.Environment.Run:41](http://github.com/zeebo/clingy.Environment.Run:41) main.main:30 runtime.main:290 ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [February 11, 2026, 10:47pm UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/18 "2026-02-11T22:47:14Z")
is this log from what? ---
**Author:** ![vladro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/vladro/32/1129_2.png) [@vladro](https://forum.storj.io/u/vladro)\ **Post date:** [February 13, 2026, 5:18am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/19 "2026-02-13T05:18:24Z")
i executed write-hashtbl.exe C:\link\1-3\30\hashstore\12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S\s0 it runs with following result: Record count=2501009 Using logSlots=23 The file exists. main.(\*cmdRoot).Execute:97 [github.com/zeebo/clingy.(\*Environment).dispatchDesc:129](http://github.com/zeebo/clingy.(*Environment).dispatchDesc:129) [github.com/zeebo/clingy.Environment.Run:41](http://github.com/zeebo/clingy.Environment.Run:41) main.main:30 runtime.main:290 but node is not starting with following error: > **Summary** > > 2026-02-13T08:05:12+03:00 FATAL Unrecoverable error {“error”: “Failed to create storage node peer: hashstore: read c:\link\1-3\30\hashstore\12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S\s0\meta\hashtbl-000000000000007a: Data error (cyclic redundancy check).\n\tstorj.io/storj/storagenode/hashstore.(\*roBigPageCache).ReadRecord:649\n\tstorj.io/storj/storagenode/hashstore.(\*HashTbl).Range:320\n\tstorj.io/storj/storagenode/hashstore.(\*HashTbl).loadEntries:264\n\tstorj.io/storj/storagenode/hashstore.OpenHashTbl:176\n\tstorj.io/storj/storagenode/hashstore.OpenTable:120\n\tstorj.io/storj/storagenode/hashstore.NewStore:261\n\tstorj.io/storj/storagenode/hashstore.New:110\n\tstorj.io/storj/storagenode/piecestore.(\*HashStoreBackend).getDB:271\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:122\n\tstorj.io/storj/storagenode.New:607\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(\*Command).execute:985\n\tgithub.com/spf13/cobra.(\*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(\*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:80\n\tstorj.io/common/process.ExecWithCustomConfig:75\n\tstorj.io/common/process.Exec:65\n\tmain.(\*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(\*Group).Go.func1:93”, “errorVerbose”: “Failed to create storage node peer: hashstore: read c:\link\1-3\30\hashstore\12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S\s0\meta\hashtbl-000000000000007a: Data error (cyclic redundancy check).\n\tstorj.io/storj/storagenode/hashstore.(\*roBigPageCache).ReadRecord:649\n\tstorj.io/storj/storagenode/hashstore.(\*HashTbl).Range:320\n\tstorj.io/storj/storagenode/hashstore.(\*HashTbl).loadEntries:264\n\tstorj.io/storj/storagenode/hashstore.OpenHashTbl:176\n\tstorj.io/storj/storagenode/hashstore.OpenTable:120\n\tstorj.io/storj/storagenode/hashstore.NewStore:261\n\tstorj.io/storj/storagenode/hashstore.New:110\n\tstorj.io/storj/storagenode/piecestore.(\*HashStoreBackend).getDB:271\n\tstorj.io/storj/storagenode/piecestore.NewHashStoreBackend:122\n\tstorj.io/storj/storagenode.New:607\n\tmain.cmdRun:84\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(\*Command).execute:985\n\tgithub.com/spf13/cobra.(\*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(\*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:80\n\tstorj.io/common/process.ExecWithCustomConfig:75\n\tstorj.io/common/process.Exec:65\n\tmain.(\*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(\*Group).Go.func1:93\n\tmain.cmdRun:86\n\tmain.newRunCmd.func1:33\n\tstorj.io/common/process.InitBeforeExecute.func1.2:389\n\tstorj.io/common/process.InitBeforeExecute.func1:407\n\tgithub.com/spf13/cobra.(\*Command).execute:985\n\tgithub.com/spf13/cobra.(\*Command).ExecuteC:1117\n\tgithub.com/spf13/cobra.(\*Command).Execute:1041\n\tstorj.io/common/process.ExecWithCustomOptions:115\n\tstorj.io/common/process.ExecWithCustomConfigAndLogger:80\n\tstorj.io/common/process.ExecWithCustomConfig:75\n\tstorj.io/common/process.Exec:65\n\tmain.(\*service).Execute.func1:107\n\tgolang.org/x/sync/errgroup.(\*Group).Go.func1:93”} ---
**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_22734026db12803ebb3e059622ac3534.png) [@Vadim](https://forum.storj.io/u/Vadim)\ **Post date:** [February 13, 2026, 5:33am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/20 "2026-02-13T05:33:25Z")
Did you put new made file instead of old in this folder meta? ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [February 13, 2026, 6:03am UTC](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359/21 "2026-02-13T06:03:36Z")
> [@vladro](#): > > The file exists. You didn’t remove the previous hashtbl from the current directory before running the tool. It’s exited without modifications, so the problem was not solved. [Next page](https://forum.storj.io/t/write-hashtbl-hashstore-collision-detected/31359.md?page=2)