disk_watch: rebase on main's merged fix, keep the shared-volume rationale in the module doc
This commit is contained in:
parent
c3e6e23d22
commit
8a7a450240
1 changed files with 8 additions and 0 deletions
|
|
@ -16,6 +16,14 @@
|
|||
//! into a new bucket (or a change in which directories are big enough to
|
||||
//! list) speaks up again. Dropping back under the threshold clears the
|
||||
//! todo.
|
||||
//!
|
||||
//! Scoped by design: the `statvfs` reads the *whole filesystem*, which on
|
||||
//! a shared host volume (several agents' state dirs on the same
|
||||
//! subvolume) can sit over threshold because of bytes some other agent
|
||||
//! owns. The todo only fires when this agent's own tree ([`big_dirs`])
|
||||
//! actually contains something big enough to name — an agent whose own
|
||||
//! footprint is negligible has nothing it can safely free, so it stays
|
||||
//! silent instead of nagging everyone on a crowded volume.
|
||||
|
||||
use std::ffi::CString;
|
||||
use std::fmt::Write as _;
|
||||
|
|
|
|||
Loading…
Reference in a new issue