mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

response

Browse source
This commit is contained in:
Joey Hess 2025-06-13 08:47:19 -04:00
parent 7ea7ae34f6
commit f9273bb0c7
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

23
doc/forum/special_remote_protocol__58___How_to_identify_exactsize/comment_1_bbc07fed3ef028d5551932853dba3f45._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2025-06-13T12:35:50Z"
content="""
`git-annex examinekey --format='${bytesize}\n'`
Or `git-annex examinekey --json` and use the `bytesize` field.
(You will probably want to use `--batch` to keep a single examinekey
process running, for speed.)
Note that not all keys have a known size. Usually keys without a known size
were added with eg `git-anex addurl --fast`. Encrypted keys also won't have
a size field.
Also, when chunking is used with a special remote (without
encryption), each chunk is a key, with its size field set to the total size
of the original key. In that case there is a separate chunk size field,
although the last chunk may be smaller than its chunk size field.
If it would be useful, examinekey could have something added to it to
indicate when a key is a chunk key, and show the chunk size.
"""]]