diskusage

type Usage ¶

type Usage struct {
	ApparentBytes int64 `json:"apparent_bytes"`
	UnsharedBytes int64 `json:"unshared_bytes"`
	SharedBytes   int64 `json:"shared_bytes"`
	Files         int64 `json:"files"`
}

Usage is one measured tree. ApparentBytes counts each inode's logical size once, the way `du --apparent-size` does. UnsharedBytes counts the physical blocks of the inodes whose every link lives inside the measured tree — the bytes removing the tree would return to the filesystem. SharedBytes is the apparent remainder: content the tree holds a link to but does not own.

func Measure(ctx context.Context, root string) (Usage, error)

func (u Usage) Add(other Usage) Usage

type Walk ¶

type Walk struct {
	// contains filtered or unexported fields
}

Walk measures several trees as one accounting unit.

Summing per-tree measurements is wrong across a fleet, and wrong in both directions. Two worktrees that hard-link the same pnpm store file each report its apparent size, so the total double-counts it; and when the only links to a file live in two measured worktrees, each tree calls it shared with something outside itself, so the total under-reports what removing both would return. A Walk answers the question a reclaim footer is actually asking — "how much comes back if I remove all of these?" — by counting every inode once and treating it as unshared exactly when every link to it is inside the selected set.

func NewWalk() *Walk

func (w *Walk) Measure(ctx context.Context, root string) (Usage, error)

func (w *Walk) Total(roots ...string) Usage