QingStor

At a glance

Capability	Support
rclone support tier	Tier 3: Supported
Checksums	MD5
Modification times	Not kept: files show their upload time
Case-insensitive names	No
Duplicate names allowed	No
Server-side copy	Yes
Server-side move and rename	No
Folder move and rename	No: each file is moved in turn
Free space reporting	No
Empty folders	No: folders exist only while they hold files
Change notifications	No
Uploads of unknown size	No
Public links	No

From rclone’s documentation

The rest of this page is adapted from rclone’s documentation for this backend (rclone v1.75.2, MIT licence). It is written for rclone’s command line: where it mentions a flag such as --qingstor-example, set the option example in the wizard’s options instead. Commands such as rclone copy aren’t part of CloudMount.

command.) You may put subdirectories in too, e.g. remote:bucket/path/to/dir.

Setup notes

In CloudMount you add this drive from the Add drive screen, and the wizard asks for the options listed under Options. The notes below come from rclone’s setup guide.

--fast-list

This remote supports --fast-list which allows you to use fewer transactions in exchange for more memory. See the rclone docs for more details.

Multipart uploads

rclone supports multipart uploads with QingStor which means that it can upload files bigger than 5 GiB. Note that files uploaded with multipart upload don’t have an MD5SUM.

Note that incomplete multipart uploads older than 24 hours can be removed with rclone cleanup remote:bucket just for one bucket rclone cleanup remote: for all buckets. QingStor does not ever remove incomplete multipart uploads so it may be necessary to run this from time to time.

Buckets and Zone

With QingStor you can list buckets (rclone lsd) using any zone, but you can only access the content of a bucket from the zone it was created in. If you attempt to access a bucket from the wrong zone, you will get an error, incorrect zone, the bucket is not in 'XXX' zone.

Authentication

There are two ways to supply rclone with a set of QingStor credentials. In order of precedence:

• Directly in the rclone configuration file (as configured by rclone config)
  • set access_key_id and secret_access_key
• Runtime configuration:
  • set env_auth to true in the config file
  • Exporting the following environment variables before running rclone
    • Access Key ID: QS_ACCESS_KEY_ID or QS_ACCESS_KEY
    • Secret Access Key: QS_SECRET_ACCESS_KEY or QS_SECRET_KEY

Restricted filename characters

The control characters 0x00-0x1F and / are replaced as in the default restricted characters set. Note that 0x7F is not replaced.

Invalid UTF-8 bytes will also be replaced, as they can’t be used in JSON strings.

Options

Standard options

The wizard asks for these when you add the drive.

env_auth

Get QingStor credentials from runtime.

Only applies if access_key_id and secret_access_key is blank.

Type: bool · Default: false

Choices:

• false: Enter QingStor credentials in the next step.
• true: Get QingStor credentials from the environment (env vars or IAM).

access_key_id

QingStor Access Key ID.

Leave blank for anonymous access or runtime credentials.

Type: string

secret_access_key

QingStor Secret Access Key (password).

Leave blank for anonymous access or runtime credentials.

Type: string

endpoint

Enter an endpoint URL to connection QingStor API.

Leave blank will use the default value “https://qingstor.com:443”.

Type: string

zone

Zone to connect to.

Default is “pek3a”.

Type: string

Choices:

• pek3a: The Beijing (China) Three Zone. Needs location constraint pek3a.
• sh1a: The Shanghai (China) First Zone. Needs location constraint sh1a.
• gd2a: The Guangdong (China) Second Zone. Needs location constraint gd2a.

Advanced options

The wizard shows these under Advanced options. Most drives work without changing any of them.

connection_retries

Number of connection retries.

Type: int · Default: 3

upload_cutoff

Cutoff for switching to chunked upload.

Any files larger than this will be uploaded in chunks of chunk_size. The minimum is 0 and the maximum is 5 GiB.

Type: SizeSuffix · Default: 200Mi

chunk_size

Chunk size to use for uploading.

When uploading files larger than upload_cutoff they will be uploaded as multipart uploads using this chunk size.

Note that “–qingstor-upload-concurrency” chunks of this size are buffered in memory per transfer.

If you are transferring large files over high-speed links and you have enough memory, then increasing this will speed up the transfers.

Type: SizeSuffix · Default: 4Mi

upload_concurrency

Concurrency for multipart uploads.

This is the number of chunks of the same file that are uploaded concurrently.

NB if you set this to > 1 then the checksums of multipart uploads become corrupted (the uploads themselves are not corrupted though).

If you are uploading small numbers of large files over high-speed links and these uploads do not fully utilize your bandwidth, then increasing this may help to speed up the transfers.

Type: int · Default: 1

encoding

The encoding for the backend.

See the encoding section in the overview for more info.

Type: Encoding · Default: Slash,Ctl,InvalidUtf8

description

Description of the remote.

Type: string

Limitations

rclone about is not supported by the qingstor backend. Backends without this capability cannot determine free space for an rclone mount or use policy mfs (most free space) as a member of an rclone union remote.

See List of backends that do not support rclone about and rclone about.