desync(1)

πŸ“¦
version 1.1.5 Β· 3 versions
, in arch rolling

πŸ’… desync(1) β€” inspect-chunks, bestie edition πŸŽ€

okay so before we even get into it: this whole page is about desync, and specifically the inspect-chunks command inside it. yes, that desync. the icon. stay with me 🫢


✨ NAME ✨

desync-inspect-chunks β€” literally just Inspect chunks from an index and an optional local store. that's the whole vibe. πŸ’–


🌸 SYNOPSIS 🌸

desync inspect-chunks <index> [<output>] [flags]

πŸ¦‹ DESCRIPTION πŸ¦‹

so what this does: it Prints a detailed JSON with information about chunks stored in an index file. yes bestie, JSON. we love a structured data moment πŸ’…

and here's the cute part β€” if you use the --store option to provide a local store, the generated JSON will include, if available, the chunks compressed size info from that particular store. so like, you get the extra tea from that specific store. no cap. ✨


πŸ‘‘ OPTIONS πŸ‘‘

  • --ca-cert="" β€” trust authorities in this file, instead of OS trust store. iykyk πŸ”₯
  • -r, --cache-repair[=true] β€” replace invalid chunks in the cache from source. glow-up for your cache πŸ’–
  • --client-cert="" β€” path to client certificate for TLS authentication πŸ”
  • --client-key="" β€” path to client key for TLS authentication πŸ—οΈ
  • -n, --concurrency=10 β€” number of concurrent goroutines, -1 to let desync choose: the number of CPUs for chunking and hashing, adapting to each store up to 128 for transfers. it's giving main character energy, multitasking era ⚑
  • -e, --error-retry=3 β€” number of times to retry in case of network error. resilience queen 🌈
  • -b, --error-retry-base-interval=500ms β€” initial retry delay, increases linearly with each subsequent attempt. patient and linear about it 🧚
  • -h, --help[=false] β€” help for inspect-chunks. we stan a self-aware command πŸŽ€
  • -s, --store="" β€” local source store. the optional bestie 🫢
  • -t, --trust-insecure[=false] β€” trust invalid certificates. > careful bestie β€” this one literally trusts invalid certificates, so know what you're doing πŸ’€

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

these ones come from the parent, so they're like, always in the room: 🌸

  • --config="" β€” config file (default $HOME/.config/desync/config.json) πŸ—‚οΈ
  • --digest="sha512-256" β€” digest algorithm, sha512-256 or sha256 ⭐
  • --verbose[=false] β€” verbose mode. give me all the details fr fr πŸ’¬

πŸ“ EXAMPLE πŸ“

like, literally just:

  desync inspect-chunks file.caibx
  desync inspect-chunks --store /mnt/store file.caibx inspect_result.json

first one: bare minimum, iconic. second one: with a store AND an output file, ate and left no crumbs πŸ”₯


🌈 SEE ALSO 🌈

  • desync(1) β€” the parent, the origin story, the blueprint πŸ‘‘

πŸ’€ HISTORY πŸ’€

20-Oct-2026 β€” Auto generated by spf13/cobra. not me being auto generated 😭 the robots did this one.


and that's the whole page bestie ✨ this gorgeous little number is desync, manual page desync(1), dated Oct 2026. mwah, go inspect some chunks πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from