For IDE disks, dma settings are quite important to performance.
Those two commands show whether DMA is enabled on an IDE drive, and if it is, what kind. hdparm -d1 /dev/hda will attempt to enable DMA transfer on an IDE drive if it isn't already.
Hello all,
I just stuck up in an uncertain situation related to network performance...
I am trying to access one of my remote client unix machine from a distant location..
The client machine is Ultra-5_10 , with SunOS 5.5.1
The ndd result ( hme1 )shows that the machine is hooked to a... (5 Replies)
We have a AIX v5.3 on a p5 system with a poor performing Ingres database.
We added one CPU to the system to see if this would help. Now there are two CPU's.
with sar and topas -P I see good results: CPU usage around 30%
with topas I only see good results in the process output screen, the... (1 Reply)
Hi,
on a linux server I have the following :
vmstat 2 10
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 4 0 675236 39836 206060 1617660 3 3 3 6 8 7 1 1 ... (1 Reply)
Hi Gurus,
I am beginner in solaris and want to know what are the things we need to check for performance monitoring on our solairs OS.
for DISK,CPU and MEMORY.
Also how we do ipforwarding in slaris
Many thanks for your help
Pradeep P (4 Replies)
Hi All,
I have the following script which I use in Nagios to check the health of the applications, the problem with it is that the curl part ($TOTAL) does not return anything after running for 2-3 hrs, even though from command line the script runs fine but not from Nagios.
There are 17... (1 Reply)
hi I am having a performance issue with the following requirement
i have to create a permutation and combination on a set of three files
such that each record in each file is picked and the output is redirected in
a specific format but it is taking around 70 odd hours to prepare a
combination... (7 Replies)
Hi,
We have 2 lpars on p6 blade. One of the lpar is having 3 core cpu with 5gb memory running sybase as database. An EOD process takes 25 min. to complete.
Now we have an lpar on P7 server with entitled cpu capacity of 2 with 16 Gb memory and sybase as database. The EOD process which takes... (17 Replies)
Hi
We have an AIX5.3 server with application which is written in C. We are facing server (lpar) hangs intermediately. If we open new telnet window prompts for user and takes hell of a time to authenticate, not only that if we run ps -aef then also it takes lot of time. surprisingly there is no... (2 Replies)
IN solaris, for network high-availability we are using IPMP concept, can u tell me in REDHAT LINUX what we are using... also pls share good step to read & understand the that concept...
Also performance issue in linux what are step & cmd can u tell me??? (2 Replies)
Discussion started by: tiger09
2 Replies
LEARN ABOUT REDHAT
smartctl
SMARTCTL(8) System Manager's Manual SMARTCTL(8)NAME
smartctl - S.M.A.R.T. control utility
SYNOPSIS
smartctl [-cdeglostv] [device]
DESCRIPTION
smartctl controls the Self-Monitoring, Analysis and Reporting Technology System(S.M.A.R.T.) built into ATA-3 and later IDE and SCSI-3 Hard
Drives. This is used to check the reliability of the hard drive and predict drive failures. TapeAlerts support for SCSI tape drives and
changers smartctl is command line utility designed to perform simple S.M.A.R.T. tasks.
OPTIONS
smartctl accepts two agruments, options and device in respective order. The options begin with a '-' and multiple options should be begun
with a single '-'. The second argument is the device to be controled. ATA device use the form "/dev/hd*" and SCSI devices use the form
"/dev/sd*". SCSI devices use only options a,i,c,e,d. For SCSI Tape Drives and Changers with TapeAlerts support use the form "/dev/st*" and
"/dev/sg*". TapeAlerts devices use only a,i,c,e,d.
i Check if the device supports S.M.A.R.T
c Check if device has any S.M.A.R.T. Warranty Failures
g Prints only the generic S.M.A.R.T. attributes
v Prints only the vendor specific S.M.A.R.T. attributes
t Prints only the vendor specific S.M.A.R.T. thresholds
l Prints only the S.M.A.R.T. error log
a Prints all parameters for c,i,g,v,t,l (for SCSI c,i)
e Enables S.M.A.R.T. on device
d Disables S.M.A.R.T. on device
t Enables S.M.A.R.T. automatic offline self test timer which scans the drive every four hours for disk defects.
T Disables S.M.A.R.T. automatic offline self test timer
O Runs S.M.A.R.T. Immediate off-line Test
S Runs S.M.A.R.T. Short Self Test ( usually under ten minutes)
s Runs S.M.A.R.T. Short Self Test in Captive Mode.
( WARNING: This test will busy out drive for length of test. Only run this on drives without any mounted partitions.)
X Runs S.M.A.R.T. Extended Self Test ( tens of minutes)
x Runs S.M.A.R.T. Extended Self Test in Captive Mode. ( WARNING: This test will busy out drive for length of test. Only run this on
drives without any mounted partitions.)
A Aborts Non-Captive S.M.A.R.T. Tests.
EXAMPLES
smartctl -a /dev/hda - prints all S.M.A.R.T. infomration for drive /dev/hda (Primary Master)
smartctl -d /dev/hdd - disable S.M.A.R.T. on drive /dev/hdd (Secondary Slave)
AUTHOR
Michael Cornwell, cornwell@acm.org
Concurrent Systems Laboratory
Jack Baskin School of Engineering
University of California Santa Cruz
http://csl.cse.ucsc.edu/
smartctl-2.1 September 13, 2001 SMARTCTL(8)