xref: /titanic_44/usr/src/man/man1m/cachefswssize.1m (revision 430b4c467020edf2445feb0c21db01c88b86243a)
te
Copyright (c) 1996, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
cachefswssize 1M "16 Sep 1996" "SunOS 5.11" "System Administration Commands"
NAME
cachefswssize - determine working set size for cachefs
SYNOPSIS

cachefswssize logfile
DESCRIPTION

The cachefswssize command displays the workspace size determined from logfile. This includes the amount of cache space needed for each filesystem that was mounted under the cache, as well as a total.

USAGE

See largefile(5) for the description of the behavior of cachefswssize when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).

EXAMPLES

Example 1 A sample output of cachefswssize.

example% cachefswssize /var/tmp/samlog

/home/sam
end size:10688k
high water size:10704k
/foo
end size:128k
high water size:128k
/usr/dist
end size:1472k
high water size:1472k
total for cache
initial size:110960k
end size:12288k
high water size:12304k
EXIT STATUS

The following exit values are returned:

0

success

non-zero

an error has occurred.

SEE ALSO

cachefslog(1M), cachefsstat(1M), cfsadmin(1M), attributes(5), largefile(5)

DIAGNOSTICS

problems were encountered writing log file

There were problems encountered when the kernel was writing the logfile. The most common problem is running out of disk space.

invalid log file

The logfile is not a valid logfile or was created with a newer version of Solaris than the one where cachefswssize is running.