mode.CanSet leaves a .mode-probe-* file behind forever when the local tier turns unwritable between the probe's create and its remove (a chmod during the hook's window, or a kill between the two): CanSet reports 'removing the probe' once, the file stays, and nothing ever sweeps it. Review2 of the badge lane reproduced it: 40 probes against a chmod-flapping tier left 7 probe files. Remedy: sweep stale probe files at the top of CanSet.

mode.CanSet leaves a .mode-probe-* file behind forever when the local tier turns unwritable between the probe's create and its remove (a chmod during the hook's window, or a kill between the two): CanSet reports 'removing the probe' once, the file stays, and nothing ever sweeps it. Review2 of the badge lane reproduced it: 40 probes against a chmod-flapping tier left 7 probe files. Remedy: sweep stale probe files at the top of CanSet.

Grounds

• pursued: after a probe is orphaned, the next CanSet leaves the tier holding no probe-shaped regular file while a lookalike file and a probe-named directory survive, and concurrent probes all answer nil; a probe file surviving a later CanSet, or a concurrent probe reporting 'removing the probe', would show it wrong