10-09-2012
ZFS : Can arc size value exceed Physical RAM ?
Hi,
kstat -p -m zfs -n arcstats -s size returns
zfs:0:arcstats:size 8177310584
this values is approx (7.61 GB)
but my Physical Memory size is only 6144 Megabytes.
Can this happen ?
if yes, then how can I find free memory on the system.
BTW, I ran the kstat commands from a Non global zone.
9 More Discussions You Might Find Interesting
1. Programming
We have Sun OS 5.9 we are doing a backup process (ProC program) that uses the function...
fprintf(fp,"%s;%s;%s;%s;%s;%ld;%ld;%ld;%ld;%s;%s;%s;%d;%s;%s;%s;%ld;%s;%s;%s;%ld;%ld;%s;%ld;%s;%ld;%s;%s;%c%c",x_contrno, x_subno, x_b_subno,x_transdate,x_last_traffic_date,BillAmt_s, x_billamount_int,... (10 Replies)
Discussion started by: atiato
10 Replies
2. Solaris
What command should I be using on Solaris 9 to get an accurate representation of the available physical RAM? (4 Replies)
Discussion started by: dangral
4 Replies
3. Solaris
Hi All,
I am trying to find the physical memory usage by each process/users.
Can you please let me know how to get the memory usage?.
Thanks,
bsraj. (12 Replies)
Discussion started by: bsrajirs
12 Replies
4. Red Hat
Hi,
On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb
can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Solaris
We are having a server running zfs root with 64G RAM and the system has 3 zones running oracle fusion app and zfs cache is using 40G memory as per
kstat zfs:0:arcstats:size. and system shows only 5G of memory is free rest is taken by kernel and 2 remaining zones.
Now my problem is that... (2 Replies)
Discussion started by: fugitive
2 Replies
6. Solaris
I have a Sun T5120, and I want to programmatically determine how much RAM it has.
# uname -a
SunOS myhost 5.10 Generic_141444-09 sun4v sparc SUNW,SPARC-Enterprise-T5120
The box has 64Gb; I tried prtdiag and prtconf, but they give me bogus info
prtconf gives me:
# prtconf |grep -i... (12 Replies)
Discussion started by: thomn8r
12 Replies
7. Solaris
Greetings Forumers!
I have a Solaris 10u9 M5000 with 32GB RAM and have noticed the ZFS arc cache is consuming large amount of memory. Here's what I see on my system:
# echo ::memstat|mdb -k
Page Summary Pages MB %Tot
------------ ---------------- ... (9 Replies)
Discussion started by: bluescreen
9 Replies
8. Red Hat
Hi,
I have a server (BL460c) with 32G of physical RAM.
It currently only uses approx 5% its capacity but will use more (not sure how much more) pending the launch of further applications.
If I need to build another node of similar functionality should I consider downgrading the physical... (2 Replies)
Discussion started by: Duffs22
2 Replies
9. UNIX for Advanced & Expert Users
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
LEARN ABOUT OPENSOLARIS
kstat
kstat(9S) Data Structures for Drivers kstat(9S)
NAME
kstat - kernel statistics structure
SYNOPSIS
#include <sys/types.h>
#include <sys/kstat.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
DESCRIPTION
Each kernel statistic (kstat) exported by device drivers consists of a header section and a data section. The kstat structure is the header
portion of the statistic.
A driver receives a pointer to a kstat structure from a successful call to kstat_create(9F). Drivers should never allocate a kstat struc-
ture in any other manner.
After allocation, the driver should perform any further initialization needed before calling kstat_install(9F) to actually export the
kstat.
STRUCTURE MEMBERS
void *ks_data; /* kstat type-specif. data */
ulong_t ks_ndata; /* # of type-specif. data
records */
ulong_t ks_data_size; /* total size of kstat data
section */
int (*ks_update)(struct kstat *, int);
void *ks_private; /* arbitrary provider-private
data */
void *ks_lock; /* protects kstat's data */
The members of the kstat structure available to examine or set by a driver are as follows:
ks_data Points to the data portion of the kstat. Either allocated by kstat_create(9F) for the drivers use, or by the driver if it
is using virtual kstats.
ks_ndata The number of data records in this kstat. Set by the ks_update(9E) routine.
ks_data_size The amount of data pointed to by ks_data. Set by the ks_update(9E) routine.
ks_update Pointer to a routine that dynamically updates kstat. This is useful for drivers where the underlying device keeps cheap
hardware statistics, but where extraction is expensive. Instead of constantly keeping the kstat data section up to date,
the driver can supply a ks_update(9E) function that updates the kstat data section on demand. To take advantage of this
feature, set the ks_update field before calling kstat_install(9F).
ks_private Is a private field for the driver's use. Often used in ks_update(9E).
ks_lock Is a pointer to a mutex that protects this kstat. kstat data sections are optionally protected by the per-kstat ks_lock.
If ks_lock is non-NULL, kstat clients (such as /dev/kstat) will acquire this lock for all of their operations on that
kstat. It is up to the kstat provider to decide whether guaranteeing consistent data to kstat clients is sufficiently
important to justify the locking cost. Note, however, that most statistic updates already occur under one of the
provider's mutexes. If the provider sets ks_lock to point to that mutex, then kstat data locking is free. ks_lock is
really of type (kmutex_t*) and is declared as (void*) in the kstat header. That way, users do not have to be exposed to
all of the kernel's lock-related data structures.
SEE ALSO
kstat_create(9F)
Writing Device Drivers
SunOS 5.11 4 Apr 1994 kstat(9S)