Sponsored Content
Full Discussion: SAR -b interpretation
Top Forums UNIX for Advanced & Expert Users SAR -b interpretation Post 87617 by jim mcnamara on Wednesday 26th of October 2005 10:12:04 AM
Old 10-26-2005
Actually - what are you doing?

Unless you really have I/O problems - or disk thrashing - or some clearly defined problem, like every process is totally I/O bound, you should probably leave things alone.

It appears to me like you do not know what you are looking at, so your changing things could lead to big trouble.

Process space can also have file caches or buffers. Applications control caching (buffering) and that's where control of buffers usually should start, not at the kernel level. Look for applications that have called setvbuf() to turn off buffering, for example.

In general, disks have pretty big on-board caches, so you don't have to worry too much about the kernel cache if things are working reasonably well.

The write thing is the number of cache hits/misses - misses caused by writing new data to files; hits are a write updating an existing record in the cache, like a row in a database table.

Generally, the best thing to do is called load-leveling - placing really active directories on physically separate disks. This mostly applies to writes, but if there are lots of reports running you may also have a problem with reads bombing one disk, so move directories around in that case as well. The I/O request queue indicates the magnitude of this problem.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

shell interpretation

I executed the following command in the korn shell: $ variable1="qwerty" ls | sort and the shell executed the 'ls | sort' command. I would have expected an error message from the shell, but instead of that the shell ran the 'ls | sort' command and didn't realize the variable assignement. ... (1 Reply)
Discussion started by: PhilippeCrokaer
1 Replies

2. AIX

interpretation of sar

hello with a sar i have this result: System configuration: lcpu=48 ent=4.00 14:06:37 %usr %sys %wio %idle physc %entc 14:06:39 26 9 3 62 1.63 40.7 14:06:41 26 9 3 63 1.58 39.4 14:06:43 ... (0 Replies)
Discussion started by: pascalbout
0 Replies

3. IP Networking

DNS ENUM RR interpretation

Hi Guys, This is really really urgent. Am looking out for some quick answers. I'm developing a DNS Resolver client that interprets DNS Query repsonses & pass on the needful to DNS applications. When an ENUM query(modified to an nslookup naptr query) is issued & an NAPTR RR(Resource Record)... (1 Reply)
Discussion started by: smanu
1 Replies

4. UNIX for Dummies Questions & Answers

No Space Message Interpretation

Hi, I get the message NOTICE HTFS :No Space on dev hd (1/104), What does (1/104) mean? Is there any link, I can get material on understanding unix message log? thanks. (4 Replies)
Discussion started by: scomrade
4 Replies

5. Solaris

solaris versions interpretation

Hi What means Solaris 10 5/09 and Solaris 10 10/09, I mean the suffix 5/09 and 10/09 ? thx for help. (1 Reply)
Discussion started by: presul
1 Replies

6. Shell Programming and Scripting

Negating shell interpretation

I'm writing a Korn script but am having trouble because the shell interprets the asterisk in this case. Can anyone tell me if there is a way to fix this so that grep takes in STDIN without the interpretation? line="30 09 * * 1-4 /home/user01/bin/start" echo "$line" | grep 'start' (16 Replies)
Discussion started by: sprucio
16 Replies

7. AIX

lspath output interpretation

On my VIo I see the following for my disks: $ lspath | grep hdisk6 Enabled hdisk6 fscsi0 200600a0b82193f7,4000000000000 Enabled hdisk6 fscsi0 200700a0b82193f7,4000000000000 Enabled hdisk6 fscsi2 200600a0b82193f8,4000000000000 Failed hdisk6 fscsi2 200700a0b82193f8,4000000000000 $ lspath |... (8 Replies)
Discussion started by: petervg
8 Replies

8. UNIX for Advanced & Expert Users

Truss output interpretation

hi, anyone can help on this piece of truss output? 8094: 0.7028 write(4, 0x0043BE90, 236) = 236 8094: T S H \0\0\0EC020101\0\0\0\0\0\0\0\0\0 "02\0\0 303\0\0 I D 8094: \f %\0\0\0\0 2\0F67F\0\0\0\0 @06FFC99A ; 8094: L D6\0 303 8094: ... (6 Replies)
Discussion started by: ghostdog74
6 Replies

9. UNIX for Advanced & Expert Users

Interpretation of Ping behaviour

hi, working on Solaris 10. need your help on ping behaviour that I encountered. I ping from source to destination -bash-3.2# ping -s -t 128 10.10.10.200 PING 10.10.10.200: 56 data bytes <===== stops here for 2 minutues before getting reply back 64 bytes from 10.10.10.200:... (9 Replies)
Discussion started by: ghostdog74
9 Replies
CMDEBUG(1)						       AFS Command Reference							CMDEBUG(1)

NAME
cmdebug - Reports the status of a host Cache Manager SYNOPSIS
cmdebug -servers <machine> [-port <IP port>] [-long] [-refcounts] [-callbacks] [-ctime] [-addrs] [-cache] [-cellservdb] [-help] cmdebug -s <machine> [-p <IP port>] [-l] [-r] [-cal] [-ct] [-a] [-cac] -ce] [-h] DESCRIPTION
The cmdebug command displays information about the Cache Manager and client cache status on a local or remote AFS client machine. By default, it displays all locked cache entries, but other information can be requested via various options. CAUTIONS
The -ctime option is only available with OpenAFS version 1.4.7 and later or version 1.5.28 or later. This option can be used to gather information from any version of the Unix OpenAFS client, but can only query Windows clients running OpenAFS version 1.5.28 or later. The -cellservdb option is only available with OpenAFS version 1.4.7 and later or version 1.5.31 or later. This option can be used to gather information from any version of the Unix OpenAFS client, but can only query Windows clients running OpenAFS version 1.5.31 or later. OPTIONS
-servers <machine> Names the client machine for which to display Cache Manager status. Provide the machine's IP address in dotted decimal format, its fully qualified host name (for example, fs1.example.com), or the shortest abbreviated form of its host name that distinguishes it from other machines. Successful use of an abbreviated form depends on the availability of a name resolution service (such as the Domain Name Service or a local host table) at the time the command is issued. -port <IP port> Identifies the port on which to contact the Cache Manager. By default, the standard port 7001 is used, so this option is very rarely needed. -long Reports on all lock statuses and all cache entries, rather than only locked cache entries. Do not use this option with -refcounts, -callbacks, -addrs, -cache, or -cellservdb. -refcounts Reports only those cache entries with non-zero reference counts. Do not use this option with -long, -callbacks, -addrs, or -cache. -callbacks Reports only those cache entries with callbacks. Do not use this option with -long, -refcounts, -addrs, or -cache. -ctime Causes entry expiration times to be shown in human-readable format. Do not use this option with -addrs or -cache. -addrs Rather than showing any cache entries, displays the interfaces the Cache Manager answers on, including their netmasks and MTUs. This is useful for analyzing clients that are multihomed and identifying problems with netmasks or MTU settings. Do not use this option with -long, -refcounts, -callbacks, or -cache. -cache Rather than showing any cache entries, displays the cache configuration for the client machine. The information displayed is essentially the information that can be configured via parameters to afsd. Do not use this option with -long, -refcounts, -callbacks, or -addrs. -cellservdb Lists all known volume location database records in a CellServDB-compatible format. This includes all records in memory, including those from the CellServDB file, DNS SRV or AFSDB records, and the fs newcell command. This option could be used to see if a client has the latest copy of the CellServDB file. Do not use this option with -long, -refcounts, -callbacks, or -cache. -help Prints the online help for this command. All other valid options are ignored. EXAMPLES
Displays all of the locked cache entries on "client1": % cmdebug client1 Displays the cache configuration for "client1.example.com": % cmdebug client1.example.com -cache Displays all cache entries for "client2.example.com": % cmdebug client2.example.com -long PRIVILEGE REQUIRED
None SEE ALSO
afsd(8), CellServDB(5), fs_newcell(1) COPYRIGHT
Copyright 2005 Russ Allbery <rra@stanford.edu> This documentation is covered by the IBM Public License Version 1.0. This man page was written by Russ Allbery for OpenAFS. OpenAFS 2012-03-26 CMDEBUG(1)
All times are GMT -4. The time now is 11:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy