Skip to content

TIR Shared File System FAQ

View as Markdown

For step-by-step fixes, see Troubleshooting TIR Shared File System.

Your account’s size limit, which is 64,000 GB (64 TB) unless E2E has set a different limit for you. Once an SFS reaches that limit, you can ask E2E to raise it. See Increase the size of an SFS.

No. An SFS can only get bigger. See Increase the size of an SFS.

How many instances can use an SFS at the same time?

Section titled “How many instances can use an SFS at the same time?”

More than one. SFS is a shared, read-write file system: many instances, and the workers of a training job, can mount the same SFS at once. See Mount an SFS on an instance.

No. An SFS belongs to one project and one region, and only that project’s instances and training jobs can mount it. Create an SFS in each project that needs one.

Which permission do I need to manage an SFS?

Section titled “Which permission do I need to manage an SFS?”

The Dataset permission in your project’s policy, the same one that covers Object Storage, Block Storage, and Parallel File System. See Roles and permissions.

No. Choose the name you want to keep when you create it.

Can I choose a custom mount path for my SFS?

Section titled “Can I choose a custom mount path for my SFS?”

Yes. You set the mount path yourself when you mount the SFS on an instance or a training job. See Mount an SFS on an instance.

What happens to my data when I unmount an SFS from an instance?

Section titled “What happens to my data when I unmount an SFS from an instance?”

It stays where it is. Unmounting only removes the connection between the instance and the SFS, so the SFS and its data are ready to mount again on this instance or another one. See Mount an SFS on an instance.

Can I mount an SFS on a bare metal server or my local machine?

Section titled “Can I mount an SFS on a bare metal server or my local machine?”

No. Only TIR instances and training jobs can mount an SFS. To move data out of TIR, copy it from an instance that has the SFS mounted, for example over SSH. See Copy files to and from an instance.

Can I run Docker from a file system mounted on my instance?

Section titled “Can I run Docker from a file system mounted on my instance?”

No. An instance is itself a container and cannot run the Docker daemon, whatever you mount on it or where you install from. See Can I run Docker inside an instance?

Does my SFS disappear when I delete the instance that had it mounted?

Section titled “Does my SFS disappear when I delete the instance that had it mounted?”

No. The SFS stays in your project after you delete an instance or a training job that had it mounted. It is ready to mount elsewhere, and stays until you delete it yourself. See Delete an SFS.

What happens to my data if I delete the SFS?

Section titled “What happens to my data if I delete the SFS?”

It is deleted along with the SFS, and the delete is permanent. Copy anything you need before you delete it. See Delete an SFS.

Copy it to TIR Datasets, or sync it to storage outside TIR, on a schedule that matches how often it changes. See Delete an SFS for what to check before you delete one.

By the GB of size you set, at a monthly rate that is charged hourly and prorated. The charge runs from creation until you delete the SFS. For prices, see E2E Networks pricing.

Are there any extra charges on top of the per-GB price?

Section titled “Are there any extra charges on top of the per-GB price?”

No. The per-GB price is the only charge. It covers moving data between an SFS and an instance, and API calls. For prices, see E2E Networks pricing.

Am I charged while no instance is using my SFS?

Section titled “Am I charged while no instance is using my SFS?”

Yes. The charge runs from creation to deletion, including any time the SFS sits unmounted. To stop the charge, delete the SFS. See Delete an SFS.

What happens to billing when I resize my SFS?

Section titled “What happens to billing when I resize my SFS?”

Billing switches to the new size from the moment you resize, so the time before the resize is billed at the old size. See Increase the size of an SFS.

A charge named SFS_DISTRIBUTED_JOB appears on my bill. What is it?

Section titled “A charge named SFS_DISTRIBUTED_JOB appears on my bill. What is it?”

Every SFS, whether you created it under Storage or for a training job, is billed under this same line. To find the SFS behind it, open Shared File System in each project and region where you have one.