Project File System Migration Procedure

Posted on November 03, 2025 by Dani Cannella

1 /project is now read-only. Learn how to migrate data from /project to /project2.

After the completion of scheduled maintenance October 31 - November 2, the /project file system has been set to read-only. This change is part of the planned decommissioning of /project, which will occur on January 1, 2026.

You can no longer write data to /project—all data can be written to the /project2 file system. Any data currently left on /project can still be migrated over to /project2. If you have not yet migrated your data to /project2, please contact CARC at carc-support@usc.edu so that we can assist you.

Most user data from /project has already been transferred to /project2. Currently, your data may reside in a temporary directory on /project. We will need to coordinate with you to move this data into your allocated /project2 space and complete the final synchronization.

Below is the standard procedure for completing the final data migration steps.

2 Check your ticket

  • Most PIs already have open data migration tickets and an assigned CARC case manager.
  • If you are already in contact with your CARC case manager, please continue coordinating with them to finalize the migration.
  • If you are not a PI and you’re unsure whether your group has a migration ticket open, please email carc-support@usc.edu with the title of your project and your PIs name.
  • CARC staff will guide you through the final migration steps.

3 Final migration process

Depending on your allocation status, CARC staff will proceed as follows:

3.1 If you already have a /project2 allocation

CARC will create a new directory for you (for example: /project2/ttroj_123/project1_backup) and place your data to be migrated there.

3.2 If you do not have a /project2 allocation

Please visit hpc-account.usc.edu to request a /project2 allocation for your projects. *Note that only PIs can request allocations.*Coordinate with your assigned CARC staff member to ensure the allocation is set up correctly.

For more information see our Allocation Types and Requests user guide.

3.3 Final synchronization

Once your allocation is ready, CARC staff will schedule a time window to complete the final data synchronization. Please coordinate this schedule with your assigned CARC contact.

4 File system quotas and storage considerations

Please note the following important changes for /project2:

  • The compression ratio on /project2 is lower than that of /project—files migrated from /project will take up more disk space on /project2.
  • Due to this compression change, you may need to request a larger allocation on /project2. Your case manager will let you know the approximate allocation size you need.
  • The cost per TB on /project2 is $60/TB/year.
  • You will not be charged the new rate for Fiscal Year 26 (July 1, 2025 - June 30, 2026).
  • You have until the end of the FY26 to manage and reduce your total data volume.
  • Your FY26 bill will be based on your current allocation size on /project for only the second half of the fiscal year (January 1, 2025 – June 30, 2026).

5 Should I keep corrupt /project data?

We do not recommend retaining corrupt files from /project, as these files cannot be recovered and only consume your storage quota.

Some PIs choose to retain such files temporarily to preserve directory structures while regenerating or reorganizing project data.

If you do not specify your preference when submitting a migration request, CARC will not copy corrupt data during the transfer.

6 Need help?

If you have any questions or need assistance with your data migration, please contact us at carc-support@usc.edu.