Docs

Torch Object Storage

Mounting buckets

Mounting TOS buckets on Windows

TOS allows you to mount a TOS bucket as a local drive on Windows. This lets you manage your buckets as if they were a local file system. This topic uses a 64-bit Windows 10 operating system to demonstrate this process.

Prerequisites

Make sure your account has read and write permissions for the bucket to be mounted, and that you have obtained this account's access key ID and secret access key. For more information, see Access Key management.

You have obtained the Region ID and S3 endpoint of the bucket. For more information, see Regions and endpoints.

Notes

We recommend using Rclone to mount buckets for small-scale testing or similar scenarios. However, using Rclone in a production environment is not recommended. For production environments, use S3, TOS APIs, or TOS SDKs instead.

Step 1: Install Winfsp and Rclone

Install Winfsp as a dependency.

Download Winfsp to your local device.

Double click the installer, winfs-2.0.23075.msi, and follow the prompts to complete the installation.

Install Rclone.

Download and extract Rclone to your local device. In this example, we will extract Rclone to C:\Tools. For more information, see the Rclone forum.

Set up the environment variable path for Rclone.

On your desktop, right click My PC and select Properties.

At the bottom of the About page, click Advanced System Settings.

In the System Properties dialog box, click Environment Variables.

In the Environment Variables dialog box, under System variables, double click Path.

In the Edit environment variable dialog box, click New and enter the local path where Rclone was extracted. In this example, the path is C:\Tools\rclone-v1.57.0-windows-amd64. Then, click OK.

In the Environment Variables dialog box, click OK.

Check if the Rclone installation was successful.

On your desktop, open the search box and type cmd. Then, open the Command Prompt window.

Run this command to verify that Rclone was installed successfully.

rclone -version

If successful, the command returns output containing text similar to the following:

Usage:
rclone [flags]
rclone [command]

Step 2: Configure the connection

In the Command Prompt window, enter rclone config and press Enter to start an interactive set-up process.

Follow the instructions below to select the appropriate options and enter the required information.

tip

Select the options based on the text description, as the numbers of options may vary by Rclone version.

n) New remote //Create a new remote connection.

name> volces-tos //Enter a name for the connection. Here, we use "volces-tos".

5 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Minio, SeaweedFS, and Tencent COS
\ "s3" //Select an S3-compatible storage provider.

25 / Any other S3 compatible provider
\ "Other" //Choose "Other" for additional S3-compatible storage providers.

1 / Enter AWS credentials in the next step
\ "false" //Select "false" to input credentials in the following step.

access_key_id> AKLTYTBjY******* //Enter your access key ID (AK).

secret_access_key> TVdaaFkyRTNNa***** //Enter your secret access key (SK).

region> cn-beijing //Enter the Region ID.

endpoint> https://tos-s3-cn-beijing.volces.com //Enter the S3 endpoint.

location_constraint> //Press Enter to leave blank; keep the default value.

acl> //Press Enter to leave blank; keep the default value.

n) No (default) //Do not edit advanced settings; keep defaults.

y) Yes this is OK (default) //Review the configuration preview, then select 'y' to confirm.

q) Quit config //Exit the configuration interface.

Modify Rclone configurations.

warning

By default, Rclone uses the path style to access object storage systems, which needs to be changed to the virtual-hosted style to access TOS.

Rclone uses HTTP/2 by default. To access TOS, disable HTTP/2.

Run this command to view the path of the configuration file.

rclone config file

Open the configuration file and append the following to the connection configuration.

Parameter	Required	Description
force_path_style = false	Yes	Disables path-style access to TOS.
disable_http2 = true	Yes	Disables HTTP/2 access to TOS.
list_version = 2	No	Uses API version 2 to list objects. The API version 2 offers more comprehensive parameters and resolves the timeout issues present in the API version 1. tip If you do not include this parameter in the configuration file, add --s3-list-version 2 when using the list command. For more information, see Viewing buckets or directories.

Below is the modified configuration file.

[volces-tos]
type = s3
provider = Other
access_key_id = AKLTYTBjY*******
secret_access_key = TVdaaFkyRTNNa*****
region = cn-beijing
endpoint = https://tos-s3-cn-beijing.volces.com
force_path_style = false
disable_http2 = true
list_version = 2

Step 3: Mount the bucket as a local drive

In the Command Prompt window, type this command and press Enter.

rclone mount <remote name>:/ <drive letter>: --cache-dir <cache directory> --vfs-cache-mode writes

Parameter	Description
Remote name	Corresponds to the remote name created in Step 2: Configure the connection. In this example, we will set it to volces-tos.
Drive letter	The identifier for the drive. In this example, we will set it to F.
Cache directory	Used to store Rclone's cache. In this example, we will set it to C:\TOS_Cache.

Example:

rclone mount volces-tos:/ F: --cache-dir C:\TOS_Cache --vfs-cache-mode writes

The command returns output containing text similar to the following:

The service rclone has been started.

On your desktop, double click This PC and click the drive letter set in the previous step. In this example, we will use the "F:" drive.

If you see the bucket in the F: drive, then it has been successfully mounted as a local drive.

Related operations

In the Command Prompt window, press ctrl -c to unmount the bucket.

warning

Before unmounting the bucket, ensure that all operations, such as uploads, are complete.

FAQ

Q: After mounting the bucket locally and accessing the drive, I receive the error "Dir.Stat error: BadRequest". What should I do?

A: This error may be caused by an incorrect access key ID or secret access key. Verify and correct them in your rclone configuration file, then remount the bucket.

Last updated: 2026.08.25 10:39:45