debian-mirror-gitlab/doc/administration/lfs/index.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

463 lines
12 KiB
Markdown
Raw Normal View History

2020-04-22 19:07:51 +05:30
---
2020-10-24 23:57:45 +05:30
stage: Create
group: Source Code
2022-11-25 23:54:43 +05:30
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments"
2020-04-22 19:07:51 +05:30
disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html'
---
2021-03-11 19:13:27 +05:30
# GitLab Git Large File Storage (LFS) Administration **(FREE SELF)**
2021-01-03 14:25:43 +05:30
2023-03-04 22:38:38 +05:30
This page contains information about configuring Git LFS in self-managed GitLab instances.
For user documentation about Git LFS, see [Git Large File Storage](../../topics/git/lfs/index.md).
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
Prerequisites:
2020-04-22 19:07:51 +05:30
2023-04-23 21:23:45 +05:30
- Users need to install [Git LFS client](https://git-lfs.com/) version 1.0.1 or later.
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
## Enable or disable LFS
LFS is enabled by default. To disable it:
::Tabs
:::TabTitle Linux package (Omnibus)
1. Edit `/etc/gitlab/gitlab.rb`:
```ruby
# Change to true to enable lfs - enabled by default if not defined
gitlab_rails['lfs_enabled'] = false
```
1. Save the file and reconfigure GitLab:
```shell
sudo gitlab-ctl reconfigure
```
:::TabTitle Helm chart (Kubernetes)
1. Export the Helm values:
```shell
helm get values gitlab > gitlab_values.yaml
```
1. Edit `gitlab_values.yaml`:
```yaml
global:
appConfig:
lfs:
enabled: false
```
1. Save the file and apply the new values:
```shell
helm upgrade -f gitlab_values.yaml gitlab gitlab/gitlab
```
:::TabTitle Docker
1. Edit `docker-compose.yml`:
```yaml
version: "3.6"
services:
gitlab:
environment:
GITLAB_OMNIBUS_CONFIG: |
gitlab_rails['lfs_enabled'] = false
```
1. Save the file and restart GitLab:
```shell
docker compose up -d
```
:::TabTitle Self-compiled (source)
1. Edit `/home/git/gitlab/config/gitlab.yml`:
```yaml
production: &base
lfs:
enabled: false
```
1. Save the file and restart GitLab:
```shell
# For systems running systemd
sudo systemctl restart gitlab.target
# For systems running SysV init
sudo service gitlab restart
```
::EndTabs
## Change local storage path
2020-04-22 19:07:51 +05:30
Git LFS objects can be large in size. By default, they are stored on the server
GitLab is installed on.
2023-03-17 16:20:25 +05:30
NOTE:
For Docker installations, you can change the path where your data is mounted.
For the Helm chart, use
[object storage](https://docs.gitlab.com/charts/advanced/external-object-storage/).
To change the default local storage path location:
::Tabs
:::TabTitle Linux package (Omnibus)
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
1. Edit `/etc/gitlab/gitlab.rb`:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```ruby
# /var/opt/gitlab/gitlab-rails/shared/lfs-objects by default.
gitlab_rails['lfs_storage_path'] = "/mnt/storage/lfs-objects"
```
1. Save the file and reconfigure GitLab:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo gitlab-ctl reconfigure
```
:::TabTitle Self-compiled (source)
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
1. Edit `/home/git/gitlab/config/gitlab.yml`:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```yaml
# /home/git/gitlab/shared/lfs-objects by default.
production: &base
lfs:
storage_path: /mnt/storage/lfs-objects
```
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
1. Save the file and restart GitLab:
2021-01-03 14:25:43 +05:30
2023-03-17 16:20:25 +05:30
```shell
# For systems running systemd
sudo systemctl restart gitlab.target
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
# For systems running SysV init
sudo service gitlab restart
```
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
::EndTabs
2020-04-22 19:07:51 +05:30
## Storing LFS objects in remote object storage
2021-03-11 19:13:27 +05:30
You can store LFS objects in remote object storage. This allows you
2022-01-26 12:08:38 +05:30
to reduce reads and writes to the local disk, and free up disk space significantly.
2020-04-22 19:07:51 +05:30
2023-03-04 22:38:38 +05:30
In GitLab 13.2 and later, you should use the
2020-07-28 23:09:34 +05:30
[consolidated object storage settings](../object_storage.md#consolidated-object-storage-configuration).
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
### Migrating to object storage
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
You can migrate the LFS objects from local storage to object storage. The
processing is done in the background and requires **no downtime**.
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
1. [Configure the object storage](../object_storage.md#consolidated-object-storage-configuration).
1. Migrate the LFS objects:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
::Tabs
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Linux package (Omnibus)
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo gitlab-rake gitlab:lfs:migrate
```
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Docker
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo docker exec -t <container name> gitlab-rake gitlab:lfs:migrate
2020-04-22 19:07:51 +05:30
```
2023-03-17 16:20:25 +05:30
:::TabTitle Self-compiled (source)
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo -u git -H bundle exec rake gitlab:lfs:migrate RAILS_ENV=production
```
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
::EndTabs
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
1. Optional. Track the progress and verify that all job LFS objects migrated
successfully using the PostgreSQL console.
1. Open a PostgreSQL console:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
::Tabs
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Linux package (Omnibus)
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo gitlab-psql
```
2020-10-24 23:57:45 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Docker
2020-10-24 23:57:45 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo docker exec -it <container_name> /bin/bash
gitlab-psql
```
2020-10-24 23:57:45 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Self-compiled (source)
2020-10-24 23:57:45 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo -u git -H psql -d gitlabhq_production
```
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
::EndTabs
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
1. Verify that all LFS files migrated to object storage with the following
SQL query. The number of `objectstg` should be the same as `total`:
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
```shell
gitlabhq_production=# SELECT count(*) AS total, sum(case when file_store = '1' then 1 else 0 end) AS filesystem, sum(case when file_store = '2' then 1 else 0 end) AS objectstg FROM lfs_objects;
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
total | filesystem | objectstg
------+------------+-----------
2409 | 0 | 2409
```
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
1. Verify that there are no files on disk in the `lfs-objects` directory:
2022-08-13 15:12:31 +05:30
2023-03-17 16:20:25 +05:30
::Tabs
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Linux package (Omnibus)
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo find /var/opt/gitlab/gitlab-rails/shared/lfs-objects -type f | grep -v tmp | wc -l
```
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Docker
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
Assuming you mounted `/var/opt/gitlab` to `/srv/gitlab`:
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo find /srv/gitlab/gitlab-rails/shared/lfs-objects -type f | grep -v tmp | wc -l
```
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
:::TabTitle Self-compiled (source)
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
```shell
sudo find /home/git/gitlab/shared/lfs-objects -type f | grep -v tmp | wc -l
```
2022-01-26 12:08:38 +05:30
2023-03-17 16:20:25 +05:30
::EndTabs
2020-04-22 19:07:51 +05:30
### Migrating back to local storage
2023-03-17 16:20:25 +05:30
NOTE:
For the Helm chart, you should use
[object storage](https://docs.gitlab.com/charts/advanced/external-object-storage/).
2021-03-11 19:13:27 +05:30
To migrate back to local storage:
2020-04-22 19:07:51 +05:30
2023-03-17 16:20:25 +05:30
::Tabs
:::TabTitle Linux package (Omnibus)
1. Migrate the LFS objects:
```shell
sudo gitlab-rake gitlab:lfs:migrate_to_local
```
1. Edit `/etc/gitlab/gitlab.rb` and
2023-05-27 22:25:52 +05:30
[disable object storage](../object_storage.md#disable-object-storage-for-specific-features)
2023-03-17 16:20:25 +05:30
for LFS objects:
```ruby
gitlab_rails['object_store']['objects']['lfs']['enabled'] = false
```
1. Save the file and reconfigure GitLab:
```shell
sudo gitlab-ctl reconfigure
```
:::TabTitle Docker
1. Migrate the LFS objects:
```shell
sudo docker exec -t <container name> gitlab-rake gitlab:lfs:migrate_to_local
```
1. Edit `docker-compose.yml` and disable object storage for LFS objects:
```yaml
version: "3.6"
services:
gitlab:
environment:
GITLAB_OMNIBUS_CONFIG: |
gitlab_rails['object_store']['objects']['lfs']['enabled'] = false
```
1. Save the file and restart GitLab:
```shell
docker compose up -d
```
:::TabTitle Self-compiled (source)
1. Migrate the LFS objects:
```shell
sudo -u git -H bundle exec rake gitlab:lfs:migrate_to_local RAILS_ENV=production
```
1. Edit `/home/git/gitlab/config/gitlab.yml` and disable object storage for LFS objects:
```yaml
production: &base
object_store:
objects:
lfs:
enabled: false
```
1. Save the file and restart GitLab:
```shell
# For systems running systemd
sudo systemctl restart gitlab.target
# For systems running SysV init
sudo service gitlab restart
```
::EndTabs
2020-04-22 19:07:51 +05:30
## Storage statistics
2021-03-11 19:13:27 +05:30
You can see the total storage used for LFS objects on groups and projects:
- In the administration area.
- In the [groups](../../api/groups.md) and [projects APIs](../../api/projects.md).
2020-04-22 19:07:51 +05:30
2023-03-04 22:38:38 +05:30
## Related topics
- Blog post: [Getting started with Git LFS](https://about.gitlab.com/blog/2017/01/30/getting-started-with-git-lfs-tutorial/)
- User documentation: [Git Large File Storage (LFS)](../../topics/git/lfs/index.md)
- [Git LFS developer information](../../development/lfs.md)
2021-09-30 23:02:18 +05:30
## Troubleshooting
### Missing LFS objects
An error about a missing LFS object may occur in either of these situations:
- When migrating LFS objects from disk to object storage, with error messages like:
```plaintext
ERROR -- : Failed to transfer LFS object
006622269c61b41bf14a22bbe0e43be3acf86a4a446afb4250c3794ea47541a7
with error: No such file or directory @ rb_sysopen -
/var/opt/gitlab/gitlab-rails/shared/lfs-objects/00/66/22269c61b41bf14a22bbe0e43be3acf86a4a446afb4250c3794ea47541a7
```
(Line breaks have been added for legibility.)
- When running the
[integrity check for LFS objects](../raketasks/check.md#uploaded-files-integrity)
with the `VERBOSE=1` parameter.
The database can have records for LFS objects which are not on disk. The database entry may
[prevent a new copy of the object from being pushed](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/49241).
To delete these references:
1. [Start a rails console](../operations/rails_console.md).
1. Query the object that's reported as missing in the rails console, to return a file path:
```ruby
lfs_object = LfsObject.find_by(oid: '006622269c61b41bf14a22bbe0e43be3acf86a4a446afb4250c3794ea47541a7')
lfs_object.file.path
```
1. Check on disk or object storage if it exists:
```shell
ls -al /var/opt/gitlab/gitlab-rails/shared/lfs-objects/00/66/22269c61b41bf14a22bbe0e43be3acf86a4a446afb4250c3794ea47541a7
```
1. If the file is not present, remove the database record via the rails console:
```ruby
lfs_object.destroy
```
### LFS commands fail on TLS v1.3 server
2021-10-27 15:23:28 +05:30
If you configure GitLab to [disable TLS v1.2](https://docs.gitlab.com/omnibus/settings/nginx.html)
2021-09-30 23:02:18 +05:30
and only enable TLS v1.3 connections, LFS operations require a
[Git LFS client](https://git-lfs.github.com) version 2.11.0 or later. If you use
a Git LFS client earlier than version 2.11.0, GitLab displays an error:
```plaintext
batch response: Post https://username:***@gitlab.example.com/tool/releases.git/info/lfs/objects/batch: remote error: tls: protocol version not supported
error: failed to fetch some objects from 'https://username:[MASKED]@gitlab.example.com/tool/releases.git/info/lfs'
```
When using GitLab CI over a TLS v1.3 configured GitLab server, you must
2021-10-27 15:23:28 +05:30
[upgrade to GitLab Runner](https://docs.gitlab.com/runner/install/index.html) 13.2.0
2021-09-30 23:02:18 +05:30
or later to receive an updated Git LFS client version via
the included [GitLab Runner Helper image](https://docs.gitlab.com/runner/configuration/advanced-configuration.html#helper-image).
To check an installed Git LFS client's version, run this command:
```shell
git lfs version
```
2023-05-27 22:25:52 +05:30
### `Connection refused` errors
If you push or mirror LFS objects and receive errors like the following:
- `dial tcp <IP>:443: connect: connection refused`
- `Connection refused - connect(2) for \"<target-or-proxy-IP>\" port 443`
a firewall or proxy rule may be terminating the connection.
If connection checks with standard Unix tools or manual Git pushes are successful,
the rule may be related to the size of the request.
2023-03-04 22:38:38 +05:30
## Error viewing a PDF file
When LFS has been configured with object storage and `proxy_download` set to
`false`, [you may see an error when previewing a PDF file from the Web browser](https://gitlab.com/gitlab-org/gitlab/-/issues/248100):
```plaintext
An error occurred while loading the file. Please try again later.
```
This occurs due to Cross-Origin Resource Sharing (CORS) restrictions:
the browser attempts to load the PDF from object storage, but the object
storage provider rejects the request because the GitLab domain differs
from the object storage domain.
To fix this issue, configure your object storage provider's CORS
settings to allow the GitLab domain. See the following documentation
for more details:
2023-04-23 21:23:45 +05:30
1. [AWS S3](https://repost.aws/knowledge-center/s3-configure-cors)
2023-03-04 22:38:38 +05:30
1. [Google Cloud Storage](https://cloud.google.com/storage/docs/configuring-cors)
1. [Azure Storage](https://learn.microsoft.com/en-us/rest/api/storageservices/cross-origin-resource-sharing--cors--support-for-the-azure-storage-services).
2020-04-22 19:07:51 +05:30
## Known limitations
2021-03-11 19:13:27 +05:30
- Only compatible with the Git LFS client versions 1.1.0 and later, or 1.0.2.
2021-09-30 23:02:18 +05:30
- The storage statistics count each LFS object for
2020-04-22 19:07:51 +05:30
every project linking to it.