Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LFS push #2137

Closed
OleksanderEktos opened this issue Oct 19, 2022 · 4 comments
Closed

LFS push #2137

OleksanderEktos opened this issue Oct 19, 2022 · 4 comments
Labels
stale Issue is stale and will be closed if no further activity occurs

Comments

@OleksanderEktos
Copy link

Issue description

Ths issue is that large files are not fully loaded to the server.
Uploading 1GB file might upload it as 640MB, 300MB or even 200MB.

Bug Report

Describe how to reproduce the bug

How to reproduce:
git clone https://scm.test.net/scm/repo/adm/Test
cd Test
git lfs install
git lfs track .bin
git add .gitattributes
copy big "
.bin" file into the Test directory (I've copied Telegram.exe and renamed it into Telegram.bin)
git add "*.bin"
git commit -m "Add files"
git push
mkdir 1
cd 1
git clone https://scm.test.net/scm/repo/adm/Test
Error downloading object: test12.bin (118a0d5): Smudge error: Error downloading test12.bin (118a0d57cdd208fa45ace4c5556801525476930fbd9660c9f8e013f08ef72682): expected OID 118a0d57cdd208fa45ace4c5556801525476930fbd9660c9f8e013f08ef72682, got 23002e003e5f51b25385946f07263937b9128cf9ba0782003c4df9519aa475f3 after 948651341 bytes written

Describe your SCM-Manager setup

[SCM-Manager 2.34.0]
proxies - no

Which operating system, browser and versions do you use?

Server Linux test-scm 5.10.0-14-amd64 #1 SMP Debian 5.10.113-1 (2022-04-29) x86_64 GNU/Linux
Client git-lfs/3.2.0 (GitHub; windows amd64; go 1.18.2)

Log of the bug

root@hardi-scm:/home/scm# cat /var/log/scm/scm-manager.log
2022-10-19 11:06:58.936 [qtp2114664380-69] [6cTKh8Ajv6l] INFO sonia.scm.repository.DefaultRepositoryManager - delete repository scm/Test (1vTKh4fshL) of type git
2022-10-19 11:06:58.937 [qtp2114664380-69] [6cTKh8Ajv6l] INFO sonia.scm.io.DefaultFileSystem - destroy directory /var/lib/scm/repositories/1vTKh4fshL
2022-10-19 11:06:59.018 [qtp2114664380-69] [6cTKh8Ajv6l] INFO sonia.scm.security.DefaultAuthorizationCollector - invalidate cache, because of a received authorization event
2022-10-19 11:07:08.490 [qtp2114664380-61] [EYTKh8DE16r] INFO sonia.scm.repository.DefaultRepositoryManager - create repository scm/Test (3eTKh8DE2S) of type git
2022-10-19 11:07:08.491 [qtp2114664380-61] [EYTKh8DE16r] INFO sonia.scm.io.DefaultFileSystem - create directory /var/lib/scm/repositories/3eTKh8DE2S
2022-10-19 11:07:08.529 [qtp2114664380-61] [EYTKh8DE16r] INFO sonia.scm.security.DefaultAuthorizationCollector - invalidate cache, because of a received authorization event
2022-10-19 11:07:08.530 [qtp2114664380-61] [EYTKh8DE16r] INFO sonia.scm.security.DefaultAuthorizationCollector - invalidate cache, because of a received authorization event
2022-10-19 11:07:10.559 [qtp2114664380-69] [96TKh8DlL6w] WARN sonia.scm.repository.GitUtil - could not find repository head in directory /var/lib/scm/repositories/3eTKh8DE2S/data
2022-10-19 11:07:18.358 [qtp2114664380-64] [77TKh8Fn170] INFO sonia.scm.repository.DefaultRepositoryManager - modify repository scm/Test (3eTKh8DE2S) of type git
2022-10-19 11:08:10.926 [qtp2114664380-65] [2fTKh8TSx7S] WARN sonia.scm.repository.GitUtil - could not find repository head in directory /var/lib/scm/repositories/3eTKh8DE2S/data
2022-10-19 11:08:10.926 [qtp2114664380-65] [2fTKh8TSx7S] WARN sonia.scm.repository.spi.GitBrowseCommand - could not find head of repository scm/Test (3eTKh8DE2S), empty?
2022-10-19 11:19:32.862 [ReleaseFeedParser] [ ] INFO sonia.scm.admin.ReleaseFeedParser - Search for newer versions of SCM-Manager
2022-10-19 11:19:32.967 [ReleaseFeedParser] [ ] INFO sonia.scm.trace.LoggingExporter - received Release Feed span, which took 105ms:

Further information like screenshots

2022-10-19_09-55
2022-10-19_09-55_1

@eheimbuch
Copy link
Member

Hey, we fixed this issue recently. Could you please try it again with the latest SCM-Manager version?

The fix was released with 2.37.0: #2068

@OleksanderEktos
Copy link
Author

Yes. Tried upload test12.bin 1.37 GB (1,471,510,713 bytes) on [SCM-Manager 2.39.1]

PS C:\TMP\Test> git push
Locking support detected on remote "origin". Consider enabling it with:
$ git config lfs.https://hardi-scm.ektos.net/scm/repo/scm/Test.git/info/lfs.locksverify true
Uploading LFS objects: 100% (1/1), 2.9 GB | 2.6 MB/s, done.
Enumerating objects: 4, done.
Counting objects: 100% (4/4), done.
Delta compression using up to 4 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (4/4), 493 bytes | 246.00 KiB/s, done.
Total 4 (delta 0), reused 0 (delta 0), pack-reused 0
remote: Updating references: 100% (1/1)
To https://hardi-scm.ektos.net/scm/repo/scm/Test

  • [new branch] master -> master

2022-10-19_17-29

Downloaded 1.01Gb

@eheimbuch eheimbuch reopened this Oct 20, 2022
@eheimbuch
Copy link
Member

So this is still not working? Could you verify the checksum before and after the push?

@stale
Copy link

stale bot commented Nov 23, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issue is stale and will be closed if no further activity occurs label Nov 23, 2022
@stale stale bot closed this as completed Dec 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issue is stale and will be closed if no further activity occurs
Projects
None yet
Development

No branches or pull requests

2 participants