You can get a split down of busy logical volumes from that which might give you a better clue on narrowing it down. Something like this might help when the errors are starting to be logged:-
You can then inspect filename and see what you have in the Logical Volume section and see if anything enlightens you.
There is less point in running it for longer period as the critical bit will get lost in the general IO of other operations, but you might want to adjust the sleep to get a variety of views. You could even call this in a loop and write to a succession of log files to get a longer picture and it might be possible to translate the output into a CSV and import it to something to draw a graph.
I hope that this helps
Robin
Liverpool/Blackburn
UK
hi,
AIX 5.3
For any command(say tar command) I am getting 100% busy for my hdisk.
But my CPU and Memory is not busy and have more idle also.
Please advice for any performance analysing.
Thanks in Advance, (3 Replies)
Hi,
I'm posting my question here as I fele that what I am about to try to do must have been done already, and I don't want to re-invent the wheel.
I have recently become responsible for monitoring disk space usage for a large file system.
I would like to geenrate reports that will summise... (8 Replies)
Hi,
(AIX 5.1)
Is there any way to find the epoch timestamp for a file without having to use fancy perl (or similar) scripts? If anyone knows of a way to do this using just ksh commands it would be appreciated.
(It also appears I don't have the stat command available).
Alternatively is... (3 Replies)
I have several users connecting via a Windows-based SSH\telnet client. The previous sysadmin used FacetTerm to allow certain users to switch between multiple "windows." I'm told there are AIX-native ways to do this but I work with what I inherited.
Originally, many users were still connecting... (3 Replies)
Hi,
We have a filesystem mystery on our hands. Given:
2 machines, A and Aa.
Machine Aa is the problem machine.
Machine A is running Ubuntu, kernel 2.6.22.9 #1 SMP Wed Feb 20 08:46:16 CST 2008 x86_64 GNU/Linux. Machine Aa is running RHEL5.3, kernel 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38... (2 Replies)
Hello all,
Below is scripts to find the file following by:
30 days <- How many total file space within 30 days and not quantity
90 days
120 days
1 year
From here also I can get data space to put on PIE Chart. Following this scripts can I do some enhance from this scripts like do... (1 Reply)
Hi,
Am doing an enhancements related to monitoring a Linux disk I/O statistics.
The /proc/diskstats file is used to get the each disk I/O statistics. But, It returns the raw value.
How to calculate the Disk Queue Length and Disk Busy time from the raw values.
Guide me. (1 Reply)
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Please help with command to check the busy % for a hard disk device like hdisk5
Best regards,
Vishal (7 Replies)
Discussion started by: Vishal_dba
7 Replies
LEARN ABOUT HPUX
vxiod
vxiod(7) Miscellaneous Information Manual vxiod(7)NAME
vxiod - Veritas Volume Manager I/O daemon process control device
DESCRIPTION
The vxiod device in Veritas Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process con-
text is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continu-
ing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with a mirrored
volume in the read/writeback mode.
There are three aspects of I/O daemon operations:
o General I/O
o Error handling
o Log handling
I/O handling is achieved by an ioctl command that does not return, but instead calls the vxiod routine to wait for errors or I/O requests
and process them. When an error occurs, if there are no I/O daemons active, the I/O simply turns into a failure on that plex. If a gen-
eral I/O request is queued up when no daemons exist, then the I/O will hang forever until a daemon process is created. If I/O daemons are
active, then the I/O is put on a work queue and the daemons are awakened. A daemon takes an error request and tries to read other plexes
until a read succeeds or all plexes have been tried. Then, if the writeback facility is enabled, the daemon tries to write the good data
to each plex that failed on the read. If the write is successful, the read error is nullified. An I/O request is handled in a similar
manner.
Logging is handled in a similar manner. An ioctl command, which does not return, is issued to create a daemon for each volume which has
logging enabled. This daemon monitors two queues: one queue of I/O which was started while the log was busy (the ``log'' queue), and
another queue of requests which have been logged and now need to be started (the ``ready'' queue). I/O requests are taken from the log
queue when the log is no longer busy, and another log write is started. Completion of a log write results in all I/O requests which have
just been logged being placed on the I/O daemon's ready queue where they are immediately started.
One mechanism finds out how many I/O error daemons are running, and another mechanism allows a process to become an I/O daemon. Before a
process becomes an I/O daemon, it should close all open files and detach from the controlling tty. An I/O or logging daemon cannot be
killed except through an explicit ioctl.
FILES
/dev/vx/iod vxiod control device
SEE ALSO vxiod(1M), ioctl(2)VxVM 5.0.31.1 24 Mar 2008 vxiod(7)