PLAKAR-DIAG(1)
π PLAKAR-DIAG(1) β the plakar-diag page, but make it make sense
okay so this is the manual page for plakar-diag, from the General Commands Manual section. it's a glow-up of the official docs, same facts, better vibes. let's go π«Ά
β¨ NAME β¨
plakar-diag β bestie, this is the command that shows you detailed info about Plakar's internal structures. like, the behind-the-scenes stuff π
π¦ SYNOPSIS π¦
plakar diag
[contenttype | locks | object | packfile | snapshot | state | vfs | xattr]
πΈ DESCRIPTION πΈ
so the plakar diag command gives you detailed info about all kinds of internal data structures. what you actually see depends on which argument you hand it β main character energy, honestly β¨
here's the thing: with no arguments at all, it just displays information about the repository. no cap, that's the default vibe check π
the sub-commands are as follows, bestie:
π the sub-commands π
contenttype snapshotID:pathβ literally thecontenttypesub-command, takingsnapshotID:path. that's it, that's the spec πlocksβ displays the list of locks currently held on the repository. so you can see who's holding what πobject objectIDβ displays information about a specific object, including itsmac,type,tags, and associated data chunks. the whole lil resume for that object π₯packfile packfileIDβ shows details of packfiles, including entries andmacs, which store object data within the repository. these are the storage containers, fr fr πsnapshot snapshotIDβ shows detailed information about a specific snapshot, including its metadata, directory and file count, and size. the full 411 on that snapshot πΈstateβ lists or describes the states in the repository. yes queen, the states π§vfs snapshotID:pathβ shows filesystem (VFS) details for a specific path within a snapshot, listing directory or file attributes, including permissions, ownership, and custom metadata. the whole filesystem tea βxattr snapshotID:pathβ thexattrsub-command, takingsnapshotID:path. that's the spec, don't come for me π
π₯ EXIT STATUS π₯
the plakar-diag utility exits 0 on success, and >0 if an error occurs. so like, 0 = we ate, >0 = something went sideways π
π EXAMPLES π
show repository information β this is the no-argument classic:
$ plakar diag
show detailed information for a snapshot:
$ plakar diag snapshot abc123
list all states in the repository:
$ plakar diag state
display a specific object within a snapshot:
$ plakar diag object 1234567890abcdef
display filesystem details for a path within a snapshot:
$ plakar diag vfs abc123:/etc/passwd
π SEE ALSO π
go check these out too, iykyk:
π reminder bestie: every flag, argument, path and number up there is verbatim from the real page. i changed the vibe, not the facts. periodt β¨
π that's the whole page! π this lil cutie comes from Debian, dated May 5, 2026 β and honestly? she slays. bye bestie, go diagnose something ππ¦
π¦ where this page comes from
- nixos 26.05: plakar 1.1.4
- nixpkgs unstable: plakar 1.1.7
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms