Maintenance Commands

There are commands availabe to maintain the Infinite Scale instance. This document gives an overview of the available commands and links to the related services where they are implemented for more details.

Compared to unfinished uploads which are handled by the system, managing expired uploads can be a necessity as those files can pile up, blocking storage resources and need to be removed by command regularly. See the Manage Unfinished Uploads section at the Storage Users service for details.

This command is about purging old trash-bin items of project spaces (spaces that have been created manually) and personal spaces. See the Purge Expired Space Trash-Bin Items section at the Storage Users service for details.

In rare circumstances, it can be necessary to initiate indexing manually for a given space or user. Though the search service handles exception cases automatically, it can happen that the search service was not able to complete indexing due to a dirty shut-down of the service or because of a bug. Re-indexing should only be run on explicit request and supervision by ownCloud support. See the Manually Trigger Re-Indexing a Space section at the Search service for details.

If post-processing fails in one step due to an unforeseen error, current uploads will not be retried automatically. Starting with Infinite Scale release 4.0.0, a system administrator can instead run a CLI command to retry the failed upload.

Infinite Scale provides a CLI command with which you can inspect and manipulate node metadata.

Infinite Scale provides a CLI command with which you can inspect and repair node tree sizes. This command can be necessary in very rare cases where spaces or files are shown in the Web UI with a size not matching reality. For the repair option Infinite Scale must be shut down.

Starting with Infinite Scale release 4.0.0, a CLI command is provided to roll back or roll forward a decomposedfs migration.

Starting with Infinite Scale release 4.0.0, a CLI command is provided to repair and migrate jsoncs3 indexes. In rare circumstances the data for shares from the "Shared with others" and "Shared with me" index can be corrupted though no data is lost. When using this command, you can recreate that index and migrate it to a new layout which fixes the issue.