Storj cloudsync not implemented

Product Discussions
,
1

Hello,
I am running truenas-scale and using storj bucket as my cloudsync following this TrueNAS Integration with Storj for Secure Data Storage - Storj Docs. I am finding that every so often I get the below error. Previously I pulled the file it couldn’t check and it was succeeding. Any idea why I keep hitting this error.

Failed to set modification time: NotImplemented: A header you provided implies functionality that is not implemented
status code: 501,

2

Hello @jmallit,
Welcome to the forum!

Did you create the account using a special link or did you register directly on Storj?
Also, did you configure the Cloud Account using Storj or as Generic S3?

3

Thanks for the quick response. I registered for storj through Storj as there was the partner offer in the TrueNas Portal. I am pretty sure that I followed the documentation and created a Generic S3 access token. I did just create a new bucket and have only the failed folder syncing to it and that succeeded. Also when I unchecked the folder from the other bucket job that also succeeded.

In the Truenas portal when I look at the credentials is show as a Storj iX provider.

4

TrueNAS has two option how you can use Storj S3 credentials:

  1. The generic S3-compatible provider, then you would need to specify the Access Key, the Secret Key and the Endpoint.
  2. The Storj S3 provider, then you would need to specify only the Access Key and the Secret Key.

Which one method you have used?

But I think it’s related to a file with size greater than 5GB, which you trying to move

We have identified an issue when files >5GB are moved within TrueNAS after being uploaded via a copy or sync job and a subsequent sync job occurs. This is due to how we support server-side copy which for files <5GB is an instantaneous server-side action not requiring re-upload.Given this will take us some time to resolve, would you be able to modify your workload to not locally move objects larger than 5GB? Alternatively, you could use a copy job and make periodic deletions.

see also S3 Compatibility - UploadPartCopy · Issue #40 · storj/roadmap · GitHub

Also, could you please use a TrueCloud Backup instead? It uses less segments and has snapshots to allow you to restore version of your files without having the Object versioning enabled.