Current-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: vmstat
On Tue, Nov 10, 2020 at 05:07:10PM +0100, Lars Reichardt wrote:
> On Tue, 10 Nov 2020 12:12:14 +0000
> Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:
>
> > # vmstat -C
> > Pool cache statistics.
> > Name Spin GrpSz Full Emty PoolLayer CacheLayer Hit%
> > CpuLayer Hit% amappl 8 63 66 0 496221
> > 1592973 68.8 563372236 99.7 anonpl 60772 63 11400 0
> > 55980901 177419830 68.4 9594977028 98.2 ...
> > xhcixfer 0 15 0 0 5 8 37.5
> > 77 89.6 xhcixfer 0 15 0 0 5 11
> > 54.5 193 94.3 zfs_znode_cache 2906 15 51 0 4258698
> > 17474551 75.6 215763165 91.9 ©ÿÿ 2368 15 53
> > 0 4471316 17390812 74.3 305275419 94.3 ©ÿÿ 0
> > 15 0 0 258353 259551 0.5 277790 6.6 ©ÿÿ
> > 0 15 0 0 117290 117459 0.1 119696
> > 1.9 ©ÿÿ 0 15 0 0 74991 75197 0.3
> > 79474 5.4 ©ÿÿ 2 15 0 0 36643
> > 36739 0.3 37986 3.3 ...
> >
> >
> > interesting "Pool" name... (10G wired memory box)
> >
> >
>
> Those pool names seem clearly broken.
> It seems the box is running with a zfs pool which has it's own cache
> (ARC) which memory is entirely wired and might grow quite large.
> What does vmstat -vmC show for those pools?
Memory resource pool statistics
Name Size Requests Fail Releases Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
zfs_znode_cache 2906 15 0 0 4258698 17474551 75.6 215763165 91.9
zil_lwb_cache 0 15 0 0 0 0 nan 0 nan
©ÿÿ 2368 15 0 0 4471316 17390812 74.3 305275419 94.3
©ÿÿ 0 15 0 0 258353 259551 0.5 277790 6.6
©ÿÿ 0 15 0 0 117290 117459 0.1 119696 1.9
©ÿÿ 0 15 0 0 74991 75197 0.3 79474 5.4
©ÿÿ 2 15 0 0 36643 36739 0.3 37986 3.3
...
Thanks - I'll see if unmounting them etc helps...
Patrick
Home |
Main Index |
Thread Index |
Old Index