Sponsored Content
Full Discussion: how to find an errored disk
Operating Systems Solaris how to find an errored disk Post 302086906 by BOFH on Monday 28th of August 2006 01:31:54 PM
Old 08-28-2006
I haven't touched one in a while, but iostat -En might also list the drives.

Carl
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need script to find errored files inside directories

Hi people. I working on a script to check for files that they are suposed not to be on the directory. I mean, inside of each directory it must have some files but some could be wrong, and i want to move the files that are wrong. Ex: CSPOTGET edpst/CargadoresSPOT Historicos_Spot_MDI.zip... (4 Replies)
Discussion started by: osramos
4 Replies

2. Solaris

Softpartition State: Errored in Command MetaStat

Hi people, I have on problem when execute the command METASTAT... d60: Soft Partition Device: d10 State: Errored Size: 12582912 blocks (6.0 GB) Someone help me? Thank you very much (4 Replies)
Discussion started by: denisgomes
4 Replies

3. Solaris

format can't find a disk

Hello all, I was hoping to use a spare NAS as a ZFS fileserver and try a few things. Unfortunately it has a huge raid for data, but a small 1G system disk. As I want to use the kernel CIFS server, I need OpenSolaris, which doesn't install without all the bloated Gnomestuff (oh well) So I... (2 Replies)
Discussion started by: PatrickBaer
2 Replies

4. UNIX for Dummies Questions & Answers

How to find the disk space allocated.

Hello, I need to find the total allocated disk space for the home directory. How can i find that in unix?(in GB). Thanks. (4 Replies)
Discussion started by: kailash19
4 Replies

5. AIX

how to find out disk capacity

Hi, I would like to know how to find out disk capacity if it is assigned from the storage as a lun. as per below command , I am unable to find out disk capacity. $ bash bash-3.00$ lspv hdisk1 0001579a7fa3c086 None $ lscfg -vl hdisk1 hdisk1 ... (8 Replies)
Discussion started by: manoj.solaris
8 Replies

6. Red Hat

How to find files on a dual OS disk?

Hi, I have an HP ProLiant DL360 server with dual boot OS - CentOS and SuSE. Now the server has a motherboard issue. I move the dual OS disk AAA from the dead server to an identical server and mount it as a secondary disk. Question: How can I transfer files on disk AAA to the new server?... (1 Reply)
Discussion started by: aixlover
1 Replies

7. HP-UX

How to find out boot disk

Hi, I have two disk in a machine # ioscan -funC disk Class I H/W Path Driver S/W State H/W Type Description ================================================================== disk 0 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DH072ABAA6 ... (4 Replies)
Discussion started by: ericbj
4 Replies

8. Red Hat

Help to Find out Available disk space

I need to find available disk space for /home. $ df /home Filesystem 1K-blocks Used Available Use% Mounted on /dev/mahhh/VolGroup11-LogVol00 32281452 45028 26034172 15% / $df /home |tail -1| awk '{print $4}' 15% The above result shows the... (5 Replies)
Discussion started by: Anu_1
5 Replies

9. Red Hat

Find out the failed disk

Hi Masters, How to find out the failed disk in redhat linux (OR) How to decalare whether our hard disk goes bad ? My option is: dmesg | grep "failed" check in /var/log/messages with the kernel error. Please corrrect me if im wrong. And also i heard "smartctl" command. But it's... (2 Replies)
Discussion started by: abhay1983
2 Replies

10. Emergency UNIX and Linux Support

How to find which process using, while getting High Disk I/O?

In Our Production server I/O was very high, I Recived mail that Disk I/O was high, is it possible how to find which process Used this much I/O ? Iam Using Ubuntu server 12.04. Linux 3.9.3-x86_64-server33 (Li473-1200) 07/23/2014 _x86_64_ (8 CPU) 12:05:01 AM DEV ... (5 Replies)
Discussion started by: babinlonston
5 Replies
IOSTAT(8)						    BSD System Manager's Manual 						 IOSTAT(8)

NAME
iostat -- report I/O statistics SYNOPSIS
iostat [-CdhIKoTxz?] [-c count] [-M core] [-n devs] [-N system] [-t type,if,pass] [-w wait] [drives] DESCRIPTION
The iostat utility displays kernel I/O statistics on terminal, device and cpu operations. The first statistics that are printed are averaged over the system uptime. To get information about the current activity, a suitable wait time should be specified, so that the subsequent sets of printed statistics will be averaged over that time. The options are as follows: -c Repeat the display count times. If no repeat count is specified, the default depends on whether -w is specified. With -w the default repeat count is infinity, otherwise it is 1. -C Display CPU statistics. This is on by default, unless -d or -x is specified. -d Display only device statistics. If this flag is turned on, only device statistics will be displayed, unless -C or -T is also specified to enable the display of CPU or TTY statistics. -h Put iostat in 'top' mode. In this mode, iostat will show devices in order from highest to lowest bytes per measurement cycle. -I Display total statistics for a given time period, rather than average statistics for each second during that time period. -K In the blocks transferred display (-o), display block count in kilobytes rather then the device native block size. -M Extract values associated with the name list from the specified core instead of the default ``/dev/kmem''. -n Display up to devs number of devices. The iostat utility will display fewer devices if there are not devs devices present. -N Extract the name list from the specified system instead of the default ``/boot/kernel/kernel''. -o Display old-style iostat device statistics. Sectors per second, transfers per second, and milliseconds per seek are displayed. If -I is specified, total blocks/sectors, total transfers, and milliseconds per seek are displayed. -t Specify which types of devices to display. There are three different categories of devices: device type: da Direct Access devices sa Sequential Access devices printer Printers proc Processor devices worm Write Once Read Multiple devices cd CD devices scanner Scanner devices optical Optical Memory devices changer Medium Changer devices comm Communication devices array Storage Array devices enclosure Enclosure Services devices floppy Floppy devices interface: IDE Integrated Drive Electronics devices SCSI Small Computer System Interface devices other Any other device interface passthrough: pass Passthrough devices The user must specify at least one device type, and may specify at most one device type from each category. Multiple device types in a single device type statement must be separated by commas. Any number of -t arguments may be specified on the command line. All -t arguments are ORed together to form a matching expression against which all devices in the system are compared. Any device that fully matches any -t argument will be included in the iostat output, up to the number of devices that can be displayed in 80 columns, or the maximum number of devices specified by the user. -T Display TTY statistics. This is on by default, unless -d or -x is specified. -w Pause wait seconds between each display. If no wait interval is specified, the default is 1 second. The iostat command will accept and honor a non-integer number of seconds. Note that the interval only has millisecond granularity. Finer values will be truncated. E.g., ``-w1.0001'' is the same as ``-w1.000''. The interval will also suffer from modifications to kern.hz so your mileage may vary. -x Show extended disk statistics. Each disk is displayed on a line of its own with all available statistics. If this flag is turned on, only disk statistics will be displayed, unless -C or -T is also specified to enable the display of CPU or TTY statistics. -z If -x is specified, omit lines for devices with no activity. -? Display a usage statement and exit. The iostat utility displays its information in the following format: tty tin characters read from terminals tout characters written to terminals devices Device operations. The header of the field is the device name and unit number. The iostat utility will display as many devices as will fit in a standard 80 column screen, or the maximum number of devices in the system, whichever is smaller. If -n is specified on the command line, iostat will display the smaller of the requested number of devices, and the maximum number of devices in the system. To force iostat to display specific drives, their names may be supplied on the command line. The iostat utility will not display more devices than will fit in an 80 column screen, unless the -n argument is given on the command line to specify a maximum number of devices to display. If fewer devices are specified on the command line than will fit in an 80 column screen, iostat will show only the specified devices. The standard iostat device display shows the following statistics: KB/t kilobytes per transfer tps transfers per second MB/s megabytes per second The standard iostat device display, with the -I flag specified, shows the following statistics: KB/t kilobytes per transfer xfrs total number of transfers MB total number of megabytes transferred The extended iostat device display, with the -x flag specified, shows the following statistics: r/s read operations per second w/s write operations per second kr/s kilobytes read per second kw/s kilobytes write per second qlen transactions queue length svc_t average duration of transactions, in milliseconds %b % of time the device had one or more outstanding transactions The extended iostat device display, with the -x and -I flags specified, shows the following statistics: r/i read operations per time period w/i write operations per time period kr/i kilobytes read per time period kw/i kilobytes write per time period qlen transactions queue length tsvc_t/i total duration of transactions per time period, in seconds sb/i total time the device had one or more outstanding transactions per time period, in seconds The old-style iostat display (using -o) shows the following statistics: sps sectors transferred per second tps transfers per second msps average milliseconds per transaction The old-style iostat display, with the -I flag specified, shows the following statistics: blk total blocks/sectors transferred xfr total transfers msps average milliseconds per transaction cpu us % of cpu time in user mode ni % of cpu time in user mode running niced processes sy % of cpu time in system mode in % of cpu time in interrupt mode id % of cpu time in idle mode FILES
/boot/kernel/kernel Default kernel namelist. /dev/kmem Default memory file. EXAMPLES
iostat -w 1 da0 da1 cd0 Display statistics for the first two Direct Access devices and the first CDROM device every second ad infinitum. iostat -c 2 Display the statistics for the first four devices in the system twice, with a one second display interval. iostat -t da -t cd -w 1 Display statistics for all CDROM and Direct Access devices every second ad infinitum. iostat -t da,scsi,pass -t cd,scsi,pass Display statistics once for all SCSI passthrough devices that provide access to either Direct Access or CDROM devices. iostat -h -n 8 -w 1 Display up to 8 devices with the most I/O every second ad infinitum. iostat -dh -t da -w 1 Omit the TTY and CPU displays, show devices in order of performance and show only Direct Access devices every second ad infinitum. iostat -Iw 3 Display total statistics every three seconds ad infinitum. iostat -odICTw 2 -c 9 Display total statistics using the old-style output format 9 times, with a two second interval between each measurement/display. The -d flag generally disables the TTY and CPU displays, but since the -T and -C flags are given, the TTY and CPU displays will be displayed. SEE ALSO
fstat(1), netstat(1), nfsstat(1), ps(1), systat(1), devstat(3), gstat(8), pstat(8), vmstat(8) The sections starting with ``Interpreting system activity'' in Installing and Operating 4.3BSD. HISTORY
This version of iostat first appeared in FreeBSD 3.0. AUTHORS
Kenneth Merry <ken@FreeBSD.org> BUGS
The use of iostat as a debugging tool for crash dumps is probably limited because there is currently no way to get statistics that only cover the time immediately before the crash. BSD
December 15, 2012 BSD
All times are GMT -4. The time now is 04:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy