community
/
rclone
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: clarify backend support for setting modtime only (#5638)

This commit is contained in:
albertony 2022-06-08 16:29:35 +02:00 committed by GitHub
parent 4b358ff43b
commit 20aaeba547
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 80 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

128
docs/content/overview.md
View File

@ -14,48 +14,48 @@ show through.
Here is an overview of the major features of each cloud storage system. Here is an overview of the major features of each cloud storage system.
| Name | Hash | ModTime | Case Insensitive | Duplicate Files | MIME Type | | Name | Hash | ModTime | Case Insensitive | Duplicate Files | MIME Type |
| ---------------------------- |:-----------:|:-------:|:----------------:|:---------------:|:---------:| | ---------------------------- |:----------------:|:-------:|:----------------:|:---------------:|:---------:|
| 1Fichier | Whirlpool | No | No | Yes | R | | 1Fichier | Whirlpool | - | No | Yes | R |
| Akamai Netstorage | MD5, SHA256 | Yes | No | No | R | | Akamai Netstorage | MD5, SHA256 | R/W | No | No | R |
| Amazon Drive | MD5 | No | Yes | No | R | | Amazon Drive | MD5 | - | Yes | No | R |
| Amazon S3 (or S3 compatible) | MD5 | Yes | No | No | R/W | | Amazon S3 (or S3 compatible) | MD5 | R/W | No | No | R/W |
| Backblaze B2 | SHA1 | Yes | No | No | R/W | | Backblaze B2 | SHA1 | R/W | No | No | R/W |
| Box | SHA1 | Yes | Yes | No | - | | Box | SHA1 | R/W | Yes | No | - |
| Citrix ShareFile | MD5 | Yes | Yes | No | - | | Citrix ShareFile | MD5 | R/W | Yes | No | - |
| Dropbox | DBHASH ¹ | Yes | Yes | No | - | | Dropbox | DBHASH ¹ | R | Yes | No | - |
| Enterprise File Fabric | - | Yes | Yes | No | R/W | | Enterprise File Fabric | - | R/W | Yes | No | R/W |
| FTP | - | No | No | No | - | | FTP | - | R/W ¹⁰ | No | No | - |
| Google Cloud Storage | MD5 | Yes | No | No | R/W | | Google Cloud Storage | MD5 | R/W | No | No | R/W |
| Google Drive | MD5 | Yes | No | Yes | R/W | | Google Drive | MD5 | R/W | No | Yes | R/W |
| Google Photos | - | No | No | Yes | R | | Google Photos | - | - | No | Yes | R |
| HDFS | - | Yes | No | No | - | | HDFS | - | R/W | No | No | - |
| HTTP | - | No | No | No | R | | HTTP | - | R | No | No | R |
| Hubic | MD5 | Yes | No | No | R/W | | Hubic | MD5 | R/W | No | No | R/W |
| Internet Archive | MD5, SHA1, CRC32 | Yes | No | No | - | | Internet Archive | MD5, SHA1, CRC32 | R/W ¹¹ | No | No | - |
| Jottacloud | MD5 | Yes | Yes | No | R | | Jottacloud | MD5 | R/W | Yes | No | R |
| Koofr | MD5 | No | Yes | No | - | | Koofr | MD5 | - | Yes | No | - |
| Mail.ru Cloud | Mailru ⁶ | Yes | Yes | No | - | | Mail.ru Cloud | Mailru ⁶ | R/W | Yes | No | - |
| Mega | - | No | No | Yes | - | | Mega | - | - | No | Yes | - |
| Memory | MD5 | Yes | No | No | - | | Memory | MD5 | R/W | No | No | - |
| Microsoft Azure Blob Storage | MD5 | Yes | No | No | R/W | | Microsoft Azure Blob Storage | MD5 | R/W | No | No | R/W |
| Microsoft OneDrive | SHA1 ⁵ | Yes | Yes | No | R | | Microsoft OneDrive | SHA1 ⁵ | R/W | Yes | No | R |
| OpenDrive | MD5 | Yes | Yes | Partial ⁸ | - | | OpenDrive | MD5 | R/W | Yes | Partial ⁸ | - |
| OpenStack Swift | MD5 | Yes | No | No | R/W | | OpenStack Swift | MD5 | R/W | No | No | R/W |
| pCloud | MD5, SHA1 ⁷ | Yes | No | No | W | | pCloud | MD5, SHA1 ⁷ | R | No | No | W |
| premiumize.me | - | No | Yes | No | R | | premiumize.me | - | - | Yes | No | R |
| put.io | CRC-32 | Yes | No | Yes | R | | put.io | CRC-32 | R/W | No | Yes | R |
| QingStor | MD5 | No | No | No | R/W | | QingStor | MD5 | - ⁹ | No | No | R/W |
| Seafile | - | No | No | No | - | | Seafile | - | - | No | No | - |
| SFTP | MD5, SHA1 ² | Yes | Depends | No | - | | SFTP | MD5, SHA1 ² | R/W | Depends | No | - |
| Sia | - | No | No | No | - | | Sia | - | - | No | No | - |
| SugarSync | - | No | No | No | - | | SugarSync | - | - | No | No | - |
| Storj | - | Yes | No | No | - | | Storj | - | R | No | No | - |
| Uptobox | - | No | No | Yes | - | | Uptobox | - | - | No | Yes | - |
| WebDAV | MD5, SHA1 ³ | Yes ⁴ | Depends | No | - | | WebDAV | MD5, SHA1 ³ | R ⁴ | Depends | No | - |
| Yandex Disk | MD5 | Yes | No | No | R | | Yandex Disk | MD5 | R/W | No | No | R |
| Zoho WorkDrive | - | No | No | No | - | | Zoho WorkDrive | - | - | No | No | - |
| The local filesystem | All | Yes | Depends | No | - | | The local filesystem | All | R/W | Depends | No | - |
### Notes ### Notes
@ -84,6 +84,15 @@ storage platform has been determined to allow duplicate files, and it
is possible to create them with `rclone`. It may be that this is a is possible to create them with `rclone`. It may be that this is a
mistake or an unsupported feature. mistake or an unsupported feature.
⁹ QingStor does not support SetModTime for objects bigger than 5 GiB.
¹⁰ FTP supports modtimes for the major FTP servers, and also others
if they advertised required protocol extensions. See [this](/ftp/#modified-time)
for more details.
¹¹ Internet Archive requires option `wait_archive` to be set to a non-zero value
for full modtime support.
### Hash ### ### Hash ###
The cloud storage system supports various hash types of the objects. The cloud storage system supports various hash types of the objects.
@ -96,13 +105,36 @@ systems they must support a common hash type.
### ModTime ### ### ModTime ###
The cloud storage system supports setting modification times on Allmost all cloud storage systems store some sort of timestamp
objects. If it does then this enables a using the modification times on objects, but several of them not something that is appropriate
as part of the sync. If not then only the size will be checked by to use for syncing. E.g. some backends will only write a timestamp
default, though the MD5SUM can be checked with the `--checksum` flag. that represent the time of the upload. To be relevant for syncing
it should be able to store the modification time of the source
object. If this is not the case, rclone will only check the file
size by default, though can be configured to check the file hash
(with the `--checksum` flag). Ideally it should also be possible to
change the timestamp of an existing file without having to re-upload it.
All cloud storage systems support some kind of date on the object and Storage systems with a `-` in the ModTime column, means the
these will be set when transferring from the cloud storage system. modification read on objects is not the modification time of the
file when uploaded. It is most likely the time the file was uploaded,
or possibly something else (like the time the picture was taken in
Google Photos).
Storage systems with a `R` (for read-only) in the ModTime column,
means the it keeps modification times on objects, and updates them
when uploading objects, but it does not support changing only the
modification time (`SetModTime` operation) without re-uploading,
possibly not even without deleting existing first. Some operations
in rclone, such as `copy` and `sync` commands, will automatically
check for `SetModTime` support and re-upload if necessary to keep
the modification times in sync. Other commands will not work
without `SetModTime` support, e.g. `touch` command on an existing
file will fail, and changes to modification time only on a files
in a `mount` will be silently ignored.
Storage systems with `R/W` (for read/write) in the ModTime column,
means they do also support modtime-only operations.
### Case Insensitive ### ### Case Insensitive ###