Bruce Sterling Woodcock wrote:
Of course, this is just one-time look. You'd want to monitor your filer at multiple times during heavy load problems. If you want some more general statistics of your filer's NVRAM load over time, you can go into rc_toggle_basic mode and type wafl_susp -w. In the output you'll see values for cp_from_timer (how many times NVRAM was flushed to disk at the 10 second mark), cp_from_log_full (how many times it was flushed because the NVRAM filled up), and the all-important cp_from_cp (how many times NVRAM filled up, it tried to flush to disk, and another flush was already in progress and had not yet completed). Fush == cp == consistency point.
cp_from_timer = 30001 cp_from_snapshot = 21586 cp_from_low_water = 0 cp_from_high_water = 0 cp_from_log_full = 1198160 cp_from_timer_nvlog = 19 cp_from_cp = 3312
ratbert> uptime 10:22am up 67 days, 9:35 195691476 NFS ops, 0 CIFS ops, 110 HTTP ops
This is an F760 in a cluster. Our filers have 32MB NVRAM each. Will NetApp offer more than 32MB per filer?
Systat shows nearly constant write activity.