Editing Storj

From FileZilla Wiki
Jump to navigationJump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 156: Line 156:
 
If you're familiar with BTC, this will be recognizable as it's based on the [https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki BIP39] standard.
 
If you're familiar with BTC, this will be recognizable as it's based on the [https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki BIP39] standard.
  
You can also use your own encryption phrase.
+
=== How do I export settings from libstorj CLI? ===
 +
 
 +
First run this command to get the bridge user, password and the encryption key:
 +
 
 +
    storj export-keys
 +
 
 +
And then enter those settings into FileZilla in the Getting Started section.
 +
 
 +
=== What does it mean if I see "Wrong encryption key for at least one bucket"? ===
 +
 
 +
This means that a bucket was added using a different Encryption Key and you won't be able to download the files within that bucket as it won't be able to decrypt or verify their integrity.
 +
 
 +
=== Why does the progress bar go above 100% for uploads? ===
 +
 
 +
Files are encoded with [https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction Reed Solomon] error correction before they are uploaded to the network, so there is more data being uploaded compared to the original size of the file. This provides the ability to repair parts of the file that are missing or inaccessible. The number of parity shards is currently calculated as 2/3 of the original file size.
  
 
=== How are files encoded before being uploaded to the Storj network? ===
 
=== How are files encoded before being uploaded to the Storj network? ===
  
https://docs.storj.io/dcs/concepts/overview#what-happens-when-you-upload
+
Files are first encrypted using the Encryption Key and then encoded using Reed Solomon into various size shards. For specific details please read [https://github.com/Storj/sips/blob/master/sip-0005.md SIP5]. These shards are then uploaded to different nodes in the Storj network directly after communicating with the Storj bridge to negotiate which nodes to communicate with. After the file is uploaded, it is then mirrored to other nodes in the network, so that in the event that a shard goes missing after this initial upload, a shard can be repaired. The total number of shards that can be repaired is around 1/2 of the original file.
  
 
'''''Note:''' For larger files the time it takes to do this preparation step can be more noticeable.''
 
'''''Note:''' For larger files the time it takes to do this preparation step can be more noticeable.''
Line 166: Line 180:
 
=== Can I rename or move files? ===
 
=== Can I rename or move files? ===
  
'''Server Side Move'''
+
Not currently, this feature can be supported in the future, when file ids are unique, see deprecation messages at https://github.com/Storj/service-storage-models/blob/master/lib/models/bucketentry.js#L115-L119
  
The new uplink binary has now a server side move command. You can rename a file or move it to a different folder or even bucket. Renaming a folder is not possible at the moment. We might implement that in a future release.
+
=== What do I do if I see "Transfer rate limit" error? ===
  
FileZilla doesn't supported this feature at the moment.
+
This means that a rate limit on the number of bytes uploaded or downloaded has been reached. These are calculated time spans by hour, day and month. Accounts that have billing information entered currently do not have these rate limits, and instead have a rate limit on the total number of requests, which can be seen as a "Too many requests" error.
  
 
=== How many files can I upload? ===
 
=== How many files can I upload? ===
  
There currently isn't a hard limit an the total number of bucket entries that can be added to a bucket.
+
There currently isn't a hard limit an the total number of bucket entries that can be added to a bucket. However there is limited support for more than 5000 buckets and more than 2000 bucket entries.
  
 
=== Why can't I upload a file at the root? ===
 
=== Why can't I upload a file at the root? ===
  
 
FileZilla currently maps buckets as directories at the root level and each file within those buckets is a bucket entry. Sub-directories are created by having a forward slash in the bucket entry name, which are parsed and shown as a directory within FileZilla. For this reason, it's not possible to add a file to the root because there isn't a bucket to add a bucket entry.
 
FileZilla currently maps buckets as directories at the root level and each file within those buckets is a bucket entry. Sub-directories are created by having a forward slash in the bucket entry name, which are parsed and shown as a directory within FileZilla. For this reason, it's not possible to add a file to the root because there isn't a bucket to add a bucket entry.
 +
  
 
= Conclusion =  
 
= Conclusion =  

Please note that all contributions to FileZilla Wiki are considered to be released under the GNU Free Documentation License 1.2 (see FileZilla Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)