The Check UsageTrend can be used to interpolate the usage of a volume or aggregate into the future and send an alarm if it would get filled up within a given time. Until now this check measured the size in bytes. From now on we have an additional argument ‑‑what=size|inodes. Setting this argument to inodes tells the …

UsageTrend , our new feature that was introduced in the last RC for 3.2.0, has raised a number of questions: The check is saying that the history store is not present. Where can I find it? The -stm switch for the getter activates the history store setting. Of course, the corresponding object (aggregate|volume) has to …