2024-08-09 18:46:08 +00:00
|
|
|
# NAME
|
|
|
|
|
|
|
|
git-annex maxsize - configure maximum size of a repository
|
|
|
|
|
|
|
|
# SYNOPSIS
|
|
|
|
|
|
|
|
git annex maxsize repository size
|
|
|
|
|
|
|
|
git annex maxsize repository
|
|
|
|
|
2024-08-18 15:18:16 +00:00
|
|
|
git annex maxsize
|
|
|
|
|
2024-08-09 18:46:08 +00:00
|
|
|
# DESCRIPTION
|
|
|
|
|
|
|
|
This configures the maximum combined size of annexed files that can be
|
2024-08-18 15:18:16 +00:00
|
|
|
stored in a repository. When run with a repository but without a size,
|
2024-08-22 12:09:10 +00:00
|
|
|
it displays the currently configured maxsize. When run without any
|
|
|
|
parameters, it displays an overview of the size and maxsize of all
|
2024-08-18 15:18:16 +00:00
|
|
|
repositories.
|
2024-08-09 18:46:08 +00:00
|
|
|
|
|
|
|
The repository can be specified by git remote name or
|
|
|
|
by uuid. For the current repository, use "here".
|
|
|
|
|
|
|
|
The size can be specified using any units. For example "100 gigabytes" or
|
2024-08-22 12:09:10 +00:00
|
|
|
"0.8TB"
|
2024-08-09 18:46:08 +00:00
|
|
|
|
|
|
|
This is advisory only, it does not prevent git-annex from trying to store
|
2024-08-22 12:09:10 +00:00
|
|
|
more data in a repository. When a repository has a preferred content
|
|
|
|
expression configured using "balanced" or "sizebalanced", it will take the
|
|
|
|
maxsize into account when checking preferred content. It is still possible
|
|
|
|
for the maxsize to be exceeded, eg when there are multiple writers to the
|
|
|
|
same repository.
|
|
|
|
|
|
|
|
A hard repository size limit has to be enforced in some other way,
|
|
|
|
eg by putting the repository on a partition of the desired size.
|
|
|
|
This command can then be used to tell git-annex about that size limit.
|
2024-08-09 18:46:08 +00:00
|
|
|
|
|
|
|
For example, if a git repository is on a 1 terabyte drive, and is the only
|
|
|
|
thing stored on that drive, and `annex.diskreserve` is configured to 1
|
2024-08-22 12:09:10 +00:00
|
|
|
gigabyte, then it would make sense to run
|
|
|
|
`git-annex maxsize here "999 gigabytes"`
|
2024-08-09 18:46:08 +00:00
|
|
|
|
2024-09-09 13:32:43 +00:00
|
|
|
To stop checking maximum size of a repository, set the maxsize to 0.
|
|
|
|
|
2024-08-09 18:46:08 +00:00
|
|
|
# OPTIONS
|
|
|
|
|
2024-08-11 19:41:26 +00:00
|
|
|
* `--bytes`
|
|
|
|
|
|
|
|
Displays the maximum size in bytes, disabling the default nicer units.
|
|
|
|
|
2024-08-18 15:18:16 +00:00
|
|
|
* `--json`
|
|
|
|
|
|
|
|
Enable JSON output.
|
|
|
|
|
2024-08-11 19:41:26 +00:00
|
|
|
* The [[git-annex-common-options]](1) can also be used.
|
2024-08-09 18:46:08 +00:00
|
|
|
|
|
|
|
# SEE ALSO
|
|
|
|
|
|
|
|
[[git-annex]](1)
|
|
|
|
|
2024-08-22 12:09:10 +00:00
|
|
|
[[git-annex-preferred-content]](1)
|
|
|
|
|
2024-08-09 18:46:08 +00:00
|
|
|
# AUTHOR
|
|
|
|
|
|
|
|
Joey Hess <id@joeyh.name>
|
|
|
|
|
|
|
|
Warning: Automatically converted into a man page by mdwn2man. Edit with care.
|