Scroll to navigation

datalad create-sibling-ria(1) General Commands Manual datalad create-sibling-ria(1)


datalad create-sibling-ria - creates a sibling to a dataset in a RIA store


datalad create-sibling-ria [-h] -s NAME [-d DATASET] [--storage-name NAME] [--post-update-hook] [--shared {false|true|umask|group|all|world|everybody|0xxx}] [--group GROUP] [--storage-sibling MODE] [--existing MODE] [--trust-level TRUST-LEVEL] [-r] [-R LEVELS] [--no-storage-sibling] ria+<ssh|file>://<host>[/path]


Communication with a dataset in a RIA store is implemented via two siblings. A regular Git remote (repository sibling) and a git-annex special remote for data transfer (storage sibling) -- with the former having a publication dependency on the latter. By default, the name of the storage sibling is derived from the repository sibling's name by appending "-storage".

The store's base path is expected to not exist, be an empty directory, or a valid RIA store.

RIA store layout ~~~~~~~~~~~~~~~~

A RIA store is a directory tree with a dedicated subdirectory for each dataset in the store. The subdirectory name is constructed from the DataLad dataset ID, e.g. '124/68afe-59ec-11ea-93d7-f0d5bf7b5561', where the first three characters of the ID are used for an intermediate subdirectory in order to mitigate files system limitations for stores containing a large number of datasets.

Each dataset subdirectory contains a standard bare Git repository for the dataset.

In addition, a subdirectory 'annex' hold a standard Git-annex object store. However, instead of using the 'dirhashlower' naming scheme for the object directories, like Git-annex would do, a 'dirhashmixed' layout is used -- the same as for non-bare Git repositories or regular DataLad datasets.

Optionally, there can be a further subdirectory 'archives' with (compressed) 7z archives of annex objects. The storage remote is able to pull annex objects from these archives, if it cannot find in the regular annex object store. This feature can be useful for storing large collections of rarely changing data on systems that limit the number of files that can be stored.

Each dataset directory also contains a 'ria-layout-version' file that identifies the data organization (as, for example, described above).

Lastly, there is a global 'ria-layout-version' file at the store's base path that identifies where dataset subdirectories themselves are located. At present, this file must contain a single line stating the version (currently "1"). This line MUST end with a newline character.

It is possible to define an alias for an individual dataset in a store by placing a symlink to the dataset location into an 'alias/' directory in the root of the store. This enables dataset access via URLs of format:

Error logging ~~~~~~~~~~~~~

To enable error logging at the remote end, append a pipe symbol and an "l" to the version number in ria-layout-version (like so '1|l0).

Error logging will create files in an "error_log" directory whenever the git-annex special remote (storage sibling) raises an exception, storing the Python traceback of it. The logfiles are named according to the scheme issue with which dataset. Because logging can potentially leak personal data (like local file paths for example), it can be disabled client-side by setting the configuration variable "annex.ora-remote.<storage-sibling-name>.ignore-remote-config".


URL identifying the target RIA store and access protocol. Constraints: value must be a string

show this help message. --help-np forcefully disables the use of a pager for displaying the help message
Name of the sibling. With RECURSIVE, the same name will be used to label all the subdatasets' siblings. Constraints: value must be a string
specify the dataset to process. If no dataset is given, an attempt is made to identify the dataset based on the current working directory. Constraints: Value must be a Dataset or a valid identifier of a Dataset (e.g. a path)
Name of the storage sibling (git-annex special remote). Must not be identical to the sibling name. If not specified, defaults to the sibling name plus '-storage' suffix. If only a storage sibling is created, this setting is ignored, and the primary sibling name is used. Constraints: value must be a string
Enable git's default post-update-hook for the created sibling.
If given, configures the permissions in the RIA store for multi-users access. Possible values for this option are identical to those of `git init --shared` and are described in its documentation. Constraints: value must be a string, or value must be convertible to type bool
Filesystem group for the repository. Specifying the group is crucial when --shared=group. Constraints: value must be a string
By default, an ORA storage sibling and a Git repository sibling are created (on). Alternatively, creation of the storage sibling can be disabled (off), or a storage sibling created only and no Git sibling (only). In the latter mode, no Git installation is required on the target host. Constraints: value must be one of ('only',), or value must be convertible to type bool [Default: True]
Action to perform, if a (storage) sibling is already configured under the given name and/or a target already exists. In this case, a dataset can be skipped ('skip'), an existing target repository be forcefully re-initialized, and the sibling (re-)configured ('reconfigure'), or the command be instructed to fail ('error'). Constraints: value must be one of ('skip', 'error', 'reconfigure') [Default: 'error']
specify a trust level for the storage sibling. If not specified, the default git-annex trust level is used. 'trust' should be used with care (see the git-annex-trust man page). Constraints: value must be one of ('trust', 'semitrust', 'untrust')
if set, recurse into potential subdataset.
limit recursion into subdataset to the given number of levels. Constraints: value must be convertible to type 'int'
This option is deprecated. Use '--storage-sibling off' instead.


datalad is developed by The DataLad Team and Contributors <>.

2021-07-23 datalad create-sibling-ria 0.14.6