StorageStore

One content store: what is on disk, and what the database says should be.

The two halves are deliberately separate numbers rather than one reconciled figure. They disagree in two directions and each direction means something different — a file nothing claims is what a crash between writing bytes and writing a row leaves behind, and a row whose file is gone is what an operator emptying a directory leaves. Reporting one number would hide both.

Attributes (11)

Attribute	Type	Required	Description
id	StorageStoreId	Yes	read-only
label	string	Yes	What to call it on a page. read-only
path	string	Yes	Where it is, so du and this can be compared. read-only
files	number	Yes	Files actually there. read-only
bytes	number	Yes	What they weigh. read-only
rows	number	No	Rows pointing at a file. Absent when no table backs this store. read-only
accountedBytes	number	No	What those rows say those files weigh. Absent where the table does not record a size. read-only
capBytes	number	No	The limit an operator set, where the store has one. Absent means no limit. read-only
orphanFiles	number	Yes	Files no row claims. Reported and never cleaned up automatically. read-only
orphanBytes	number	Yes	read-only
rowsWithNoFile	number	Yes	Claims whose file is not there. The station re-fetches or re-renders these. read-only