How do I translate that into english? I assume that "Anon" is the memory used by my applications. The freelist seems to indicate to me that there's still 18G available though...
If there is still 18G free, how should the swap space become involved in this already? Don't get me wrong, I'd be thrilled if just adding some swap solves my issue, but I'd like to explain to my colleagues why that's necessary. I was the one insisting on dumping as much memory as possible into this server, and I would feel a bit silly now if it turns out we could just have created huge swap as well
Btw. I created the extra swap on my rpool, which is a mirror of 2 300GB SAS drives. My other pool is a raidz1 array of 6 1TB SATAII drives. Any reason why I should prefer one pool over the other for swap space?
Hi,
Does anyone here write cross-platform applications to be run on different Unix variants?
For some reason, an application I'm working with, when being run on machines with similar specifications, I run into "cannot allocate" errors (St9bad_alloc) on AIX but not on other platforms. Is it a... (8 Replies)
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
whats the difference between setting zone capped-memory from zoncfg and setting
rctl: name: zone.max-locked-memory .. if changed the zone.max-locked-memory with prctl it does not change in rcapstat .. but if change with rcapadm it reflects in rcapstat o/p (0 Replies)
I 'm getting following error while setting deny action for a zone.cpu-shares resource control
prctl: unable to enable deny on rctl with global flag 'no-deny' and when i check with rctladm its shows me
bash-3.00# rctladm zone.cpu-shares
zone.cpu-shares syslog=n/a ... (0 Replies)
New to the forum.
I am running CentOS release 5.3 (Final) and have run into a unique situation.
I have been able to determine that we have a swap memory leak due to an issue with an asterisk server. This specific issue takes approximately 2-3 months for enough of the swap to to be used before... (1 Reply)
Hi Experts,
Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing.
Why memory utilization on solaris always looks high?
I have statement about memory on solaris, is this true:
Memory in solaris is used for... (4 Replies)
Hi,
I am a newbee in the solaris administration. My question is how to
1. Check the total CPU and memory of a global zone.
2. Check the allocated CPU and memory for each of the residing non-global zones.
I have already tried prtconf which gives the following output
/usr/sbin/prtconf... (4 Replies)
Good Day Everyone,
Just wonder anyone has encounter AIX 6.1 Memory Performance issues ? What I have in my current scenario is we have 3 datastage servers (Segregate server and EE jobs - for those who know Datastage achitect) and 2 db servers(running HA to load balance 4 nodes partitions for... (3 Replies)
Hi,
I was wondering if any Solaris fellow out there has dealt with running Solaris 11 x86 on Local Zones for Oracle RAC (which may or may not be relevant to issue), running on HP gen h/w. Every so often could be weeks between issues or some times days, there will be a memory corruption and db... (2 Replies)
Discussion started by: crossmypath
2 Replies
LEARN ABOUT FREEBSD
swap
swap(1M) System Administration Commands swap(1M)NAME
swap - swap administrative interface
SYNOPSIS
/usr/sbin/swap -a swapname [swaplow] [swaplen]
/usr/sbin/swap -d swapname [swaplow]
/usr/sbin/swap -l
/usr/sbin/swap -s
DESCRIPTION
The swap utility provides a method of adding, deleting, and monitoring the system swap areas used by the memory manager.
OPTIONS
The following options are supported:
-a swapname Add the specified swap area. This option can only be used by the super-user. swapname is the name of the swap file: for
example, /dev/dsk/c0t0d0s1 or a regular file. swaplow is the offset in 512-byte blocks into the file where the swap area
should begin. swaplen is the desired length of the swap area in 512-byte blocks. The value of swaplen can not be less than
16. For example, if n blocks are specified, then (n-1) blocks would be the actual swap length. swaplen must be at least one
page in length. The size of a page of memory can be determined by using the pagesize command. See pagesize(1). Since the
first page of a swap file is automatically skipped, and a swap file needs to be at least one page in length, the minimum
size should be a multiple of 2 pagesize bytes. The size of a page of memory is machine dependent.
swaplow + swaplen must be less than or equal to the size of the swap file. If swaplen is not specified, an area will be
added starting at swaplow and extending to the end of the designated file. If neither swaplow nor swaplen are specified,
the whole file will be used except for the first page. Swap areas are normally added automatically during system startup by
the /sbin/swapadd script. This script adds all swap areas which have been specified in the /etc/vfstab file; for the syntax
of these specifications, see vfstab(4).
To use an NFS or local file-system swapname, you should first create a file using mkfile(1M). A local file-system swap file
can now be added to the running system by just running the swap -a command. For NFS mounted swap files, the server needs to
export the file. Do this by performing the following steps:
1. Add the following line to /etc/dfs/dfstab:
share -F nfs -o rw=clientname,root=clientname path-to-swap-file
2. Run shareall(1M).
3. Have the client add the following line to /etc/vfstab:
server:path-to-swap-file - local-path-to-swap-filenfs
--- local-path-to-swap-file -- swap ---
4. Have the client run mount:
# mount local-path-to-swap-file
5. The client can then run swap -a to add the swap space:
# swap -a local-path-to-swap-file
-d swapname Delete the specified swap area. This option can only be used by the super-user. swapname is the name of the swap file: for
example, /dev/dsk/c0t0d0s1 or a regular file. swaplow is the offset in 512-byte blocks into the swap area to be deleted. If
swaplow is not specified, the area will be deleted starting at the second page. When the command completes, swap blocks can
no longer be allocated from this area and all swap blocks previously in use in this swap area have been moved to other swap
areas.
-l List the status of all the swap areas. The output has five columns:
path The path name for the swap area.
dev The major/minor device number in decimal if it is a block special device; zeroes otherwise.
swaplo The swaplow value for the area in 512-byte blocks.
blocks The swaplen value for the area in 512-byte blocks.
free The number of 512-byte blocks in this area that are not currently allocated.
The list does not include swap space in the form of physical memory because this space is not associated with a particular
swap area.
If swap -l is run while swapname is in the process of being deleted (by swap -d), the string INDEL will appear in a sixth
column of the swap stats.
-s Print summary information about total swap space usage and availability:
allocated The total amount of swap space in bytes currently allocated for use as backing store.
reserved The total amount of swap space in bytes not currently allocated, but claimed by memory mappings for possi-
ble future use.
used The total amount of swap space in bytes that is either allocated or reserved.
available The total swap space in bytes that is currently available for future reservation and allocation.
These numbers include swap space from all configured swap areas as listed by the -l option, as well swap space in the form
of physical memory.
USAGE
On the 32-bit operating system, only the first 2 Gbytes -1 are used for swap devices greater than or equal to 2 Gbytes in size. On the
64-bit operating system, a block device larger than 2 Gbytes can be fully utilized for swap up to 2**63 -1 bytes.
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of swap: LC_CTYPE and LC_MESSAGE.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO pagesize(1), mkfile(1M), shareall(1M), getpagesize(3C), vfstab(4), attributes(5), largefile(5)WARNINGS
No check is done to determine if a swap area being added overlaps with an existing file system.
SunOS 5.10 20 Jan 2004 swap(1M)
12-10-2010
