Error Invalid path

2025-06-02T05:36:56Z    ERROR   orders  cleaning filestore archive      {"Process": "storagenode", "error": "order: ordersfile: invalid path: \".archived-orders-12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs-1746896400000000000-1746904387442679634-ACCEPTED.v1.wvUkli\"", "errorVerbose": "order: ordersfile: invalid path: \".archived-orders-12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs-1746896400000000000-1746904387442679634-ACCEPTED.v1.wvUkli\"\n\tstorj.io/storj/storagenode/orders/ordersfile.getArchivedFileInfo:177\n\tstorj.io/storj/storagenode/orders/ordersfile.GetArchivedInfo:104\n\tstorj.io/storj/storagenode/orders.(*FileStore).CleanArchive.func1:429\n\tstorj.io/storj/storagenode/orders.walkFilenamesInPath:465\n\tstorj.io/storj/storagenode/orders.(*FileStore).CleanArchive:428\n\tstorj.io/storj/storagenode/orders.(*Service).CleanArchive:156\n\tstorj.io/storj/storagenode/orders.(*Service).Run.func2:140\n\tstorj.io/common/sync2.(*Cycle).Run:102\n\tstorj.io/common/sync2.(*Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:78"}

Does this require any action from me?

Extension of file looks like a temp rsync file?
Was the node migrated with rsync recently?

2 Likes

Good catch! Yes indeed I did rsync first and then switched to rclone.
The rclone sync did a bad job on deleting non existing files at destination for whatever reason. This could be a leftover. So I guess it should be safe to delete.

1 Like

I would delete it.

My take is that worst case you miss the potential earnings of orders in that file, because it will not get reported to the satellite.

However, since it’s already an archived location, most likely it was already sent previously.

2 Likes

I guess this is what I am going to do later then. With that extension deleting is not likely to break anything.

Deleted it, no more errors. Seems to be fixed.

2 Likes