Hello,
I have the follwowing message:
# ./arcstat.pl 1
time read miss miss% dmis dm% pmis pm% mmis mm% arcsz c
Use of uninitialized value in division (/) at ./arcstat.pl line 262.
Use of uninitialized value in division (/) at ./arcstat.pl line 263.
Use of uninitialized value in division (/) at ./arcstat.pl line 268.
12:17:34 6.0G 492M 8 220M 4 271M 31 402M 9 1.8G 1.8G
Use of uninitialized value in division (/) at ./arcstat.pl line 262.
Use of uninitialized value in division (/) at ./arcstat.pl line 263.
Use of uninitialized value in division (/) at ./arcstat.pl line 268.
12:17:35 40 3 7 3 7 0 0 1 5 1.8G 1.8G
Use of uninitialized value in division (/) at ./arcstat.pl line 262.
Use of uninitialized value in division (/) at ./arcstat.pl line 263.
Use of uninitialized value in division (/) at ./arcstat.pl line 268.
12:17:36 7 1 14 1 14 0 0 1 33 1.8G 1.8G
Regards
Przemek
On Fri, Oct 01, 2010 at 11:29:34AM +0200, Christian Meier wrote:
> Hello Mike,
> thank you for your update.
>
> r...@s0011 # ./arcstat.pl 3
> time read miss miss% dmis dm% pmis pm% mmis mm% arcsz c
> 11:23:38 197K 7.8K 3 5.7K 3 2.1K 4 6.1K 5 511M 1.5G
> 11:23:41 70 0 0 0 0 0 0 0 0 511M 1.5G
> 11:23:44 76 0 0 0 0 0 0 0 0 511M 1.5G
> 11:23:47 76 0 0 0 0 0 0 0 *1.4210854715202e-14*
> 511M 1.5G
> 11:23:50 71 0 0 0 0 0 0 0 0 511M 1.5G
> 11:23:53 74 0 0 0 0 0 0 0 *1.4210854715202e-14 *
> 511M 1.5G
> 11:23:56 74 0 0 0 0 0 0 0 0 511M 1.5G
> 11:23:59 79 0 0 0 0 0 0 0 0 511M 1.5G
> 11:24:02 76 0 0 0 0 0 0 0 0 511M 1.5G
> 11:24:05 74 0 0 0 0 0 0 0 *1.4210854715202e-14*
> 511M 1.5G
> 11:24:08 93 0 1.4210854715202e-14 0 1.4210854715202e-14 0
> 0 0 0 511M 1.5G
> 11:24:11 75 0 0 0 0 0 1.4210854715202e-14 0 0
> 511M 1.5G
> 11:24:14 77 0 0 0 0 0 0 0 1.4210854715202e-14
> 511M 1.5G
>
> would be nice, if the highlighted values are also "human" readable.
>
> thank you
> Christian
> > For posterity, I'd like to point out the following:
> >
> > neel's original arcstat.pl uses a crude scaling routine that results in a
> > large loss of precision as numbers cross from Kilobytes to Megabytes to
> > Gigabytes. The 1G reported arc size case described here, could actually be
> > anywhere between 1,000,000MB and 1,999,999MB. Use 'kstat zfs::arcstats' to
> > read the arc size directly from the kstats (for comparison).
> >
> > I've updated arcstat.pl with a better scaling routine that returns more
> > appropriate results (similar to df -h human-readable output). I've also
> > added support for L2ARC stats. The updated version can be found here:
> >
> > http://github.com/mharsch/arcstat
>
> _______________________________________________
> zfs-discuss mailing list
> zfs-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Regards
Przemyslaw Bak (przemol)
--
http://przemol.blogspot.com/
----------------------------------------------------------------------
Duzi chlopcy lubia wampiry i krew.
http://linkint.pl/f2718
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
