przemol,
Thanks for the feedback. I had incorrectly assumed that any machine running
the script would have L2ARC implemented (which is not the case with Solaris
10). I've added a check for this that allows the script to work on non-L2ARC
machines as long as you don't specify L2ARC stats on th
Hello Christian,
Thanks for bringing this to my attention. I believe I've fixed the rounding
error in the latest version.
http://github.com/mharsch/arcstat
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolar
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 d
Hello Mike,
thank you for your update.
r...@s0011 # ./arcstat.pl 3
time read miss miss% dmis dm% pmis pm% mmis mm% arcszc
11:23:38 197K 7.8K 3 5.7K 3 2.1K 4 6.1K 5 511M 1.5G
11:23:41 700 00 00 00 0 511M 1.5G
11:23:44 760 00 00
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,00
Blake Irvin wrote:
> I think I need to clarify a bit.
>
> I'm wondering why arc size is staying so low, when i have 10 nfs
> clients and about 75 smb clients accessing the store via resharing (on
> one of the 10 linux nfs clients) of the zfs/nfs export. Or is it
> normal for the arc target and
I think I need to clarify a bit.
I'm wondering why arc size is staying so low, when i have 10 nfs clients and
about 75 smb clients accessing the store via resharing (on one of the 10 linux
nfs clients) of the zfs/nfs export. Or is it normal for the arc target and arc
size to match? Of note, I
Blake Irvin wrote:
> I'm using Neelakanth's arcstat tool to troubleshoot performance problems with
> a ZFS filer we have, sharing home directories to a CentOS frontend Samba box.
>
> Output shows an arc target size of 1G, which I find odd, since I haven't
> tuned the arc, and the system has 4G of
I'm using Neelakanth's arcstat tool to troubleshoot performance problems with a
ZFS filer we have, sharing home directories to a CentOS frontend Samba box.
Output shows an arc target size of 1G, which I find odd, since I haven't tuned
the arc, and the system has 4G of RAM. prstat -a tells me th
