メインコンテンツまでスキップ
This page is not translated yet. 日本語 is switched on so the navigation and URLs can be tested; the text below is the English original. Use the language selector in the header to switch back, or see the documentation home.

Mount CFS

how-to · Reviewed 2026-07-31 · FEAT-0120 Public Beta

Once CFS is provisioned for your workspace it auto-mounts to every new job and workstation. Using it requires no action. Excluding it does.

Where it appears​

The mount is listed on the Inputs page of job setup. Inside the running job it's a directory named after the CFS ID:

storage_ext_{cfs_id}

Read and write it like a local disk. Standard cp, mv, mkdir, and rm all work, as does the file explorer in a workstation desktop session.

Within your job's own folder you'll find input/, and once the job completes an output/ directory linked to work/.

Don't reorganize the work directory

Modifying work/ from outside the running job can break live tailing, which reads that directory directly. This behavior can't be changed.

A suspended workstation unmounts CFS safely and remounts it on resume: no action needed.

Disable auto-mount for one job​

MethodDisableEnable (default)
UIDeselect the CFS on the Input Files pageLeave it selected
CLI#RESCALE_AUTO_ATTACH_CLOUDFILESYSTEM=falseOmit, or "autoAttachCloudfilesystem": true
API"autoAttachCloudfilesystem": false in the request bodyOmit, or set true

Worth disabling when a job writes large volumes of intermediate data you don't want landing on shared storage, or when you want the job's data isolated from the workspace.

You can't mount CFS and an HPS on the same job

The UI won't let a job attach both a storage device and an external filesystem. If you need data from both, copy it across from a workstation first.

Upload directly to CFS​

You can put files on CFS without staging them through a job's input set. Direct uploads land at:

/enc/{username}/storage_ext_{cfs_id}/users/{username}/library/file

Two tools support it:

rescale-cli upload -p -f --copy-to-cfs
POST https://{platform-url}/api/v3/folders/copy-to-device/

This is the efficient path for a large shared baseline: upload once to CFS rather than attaching it to each job.

Two things to know about direct upload

Same-name uploads overwrite on CFS. Upload mesh.cas twice and you get two entries in your Rescale Files library but one file on CFS. The second silently replaces the first.

One file at a time. Compress a directory and upload the archive if you need to move several.

Direct upload isn't available on ITAR or government platforms.

Attaching a workstation to a job's CFS data​

A workstation mounting the same CFS sees whatever jobs have written there. This is the standard post-processing handoff, no download, no re-upload, and you get visualization hardware.

See workstation files.