Sponsored Content
Top Forums UNIX for Advanced & Expert Users Find out which process is utilising a particular hdisk Post 302075906 by tansha on Wednesday 7th of June 2006 12:18:56 PM
Old 06-07-2006
Find out which process is utilising a particular hdisk

Hi,

Can anyone suggest how I can find out which process is keeping one of my hdisk constantly busy (100%) utilisation, when I ran topas .

Thanks for your feedback
Regards
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX hdisk error

Does anyone have an idea what this means? hdisk10 is part of vg1. (vg1 has 11 hdisks) I get this msg every morning @ 5:04 CST This is the orignal message: A PROBLEM WAS DETECTED ON Fri Aug 17 03:02:09 PDT 2001 801014 The Service Request Number(s)/Probable Cause or... (2 Replies)
Discussion started by: Optimus_P
2 Replies

2. Shell Programming and Scripting

how to find the chid process id from given parent process id

how to find the chid process id from given parent process id.... (the chid process doesnot have sub processes inturn) (3 Replies)
Discussion started by: guhas
3 Replies

3. AIX

vpath to an hdisk

Is there a simply way for me to map a vpath to an hdisk on AIX 5.2? (5 Replies)
Discussion started by: 2dumb
5 Replies

4. AIX

VPATHS and HDisk/not able to add to NR-VG

When I list the PV's using lspv i see both vpath and hdisk names being listed. I got the info that each vpath is configured for 4 hdisks. Problem is I am not able to add either the hard disks in vpath to the existing non-rootvg. ? need to know the basics of vpath .. (4 Replies)
Discussion started by: nivaspIND
4 Replies

5. AIX

Flashcopy, ghost hdisk ??

Hi all, I'm getting some errors on AIX regarding Flashcopy and volume group hard disks. The script that activates flashcopy showed this errors: Recreating Flashcopy for lun01_A1 Performing syntax check... Syntax check complete. Executing script... Script execution complete. SMcli... (1 Reply)
Discussion started by: enux
1 Replies

6. AIX

Find hdisk# based on LV name

I know the lv name (i.e. dprod_0000017). #lslv dprod_0000017 LOGICAL VOLUME: dprod_0000017 VOLUME GROUP: prod01vg LV IDENTIFIER: 00cb337d00004c0000000111d8566a5a.69 PERMISSION: read/write VG STATE: active/complete LV STATE: opened/syncd TYPE: ... (2 Replies)
Discussion started by: Daniel Gate
2 Replies

7. AIX

Quorum and hdisk issue

Hi. I found an issue with my appvg present in my server.my server is a single node and not part of hacmp. pmut3# lspv hdisk0 00c5c9cf92ebb96a rootvg active hdisk1 00c5c9cfcf30eee9 appvg hdisk2 00c5c9cfcf30ef98 ... (5 Replies)
Discussion started by: newtoaixos
5 Replies

8. Programming

Find parent process (not process ID)

Hi: I have a program written in FORTRAN running on AIX platform. It is because missing of documentation and without root password, therefore we want to modify the program so that we can find out which script/program that call this FORTRAN program. I have google for few days, all of them are... (3 Replies)
Discussion started by: cstsang
3 Replies

9. Shell Programming and Scripting

Fetching hdisk sequence

Hi, Planning to implement script to fetch whether the hdisks are in proper sequence. Need output for incorrect sequence Correct #lspv hdisk0 hdisk1 hdisk2 :::::::::::: hdisk5 Incorrect sequence #lspv hdisk0 hdisk6 hdisk7 hdisk10 Any idea pls share (2 Replies)
Discussion started by: ksgnathan
2 Replies

10. AIX

How can I map hdisk# to rhdisk#?

Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies
File::Find::Rule::Extending(3)				User Contributed Perl Documentation			    File::Find::Rule::Extending(3)

NAME
File::Find::Rule::Extending - the mini-guide to extending File::Find::Rule SYNOPSIS
package File::Find::Rule::Random; use strict; # take useful things from File::Find::Rule use base 'File::Find::Rule'; # and force our crack into the main namespace sub File::Find::Rule::random () { my $self = shift()->_force_object; $self->exec( sub { rand > 0.5 } ); } 1; DESCRIPTION
File::Find::Rule went down so well with the buying public that everyone wanted to add extra features. With the 0.07 release this became a possibility, using the following conventions. Declare your package package File::Find::Rule::Random; use strict; Inherit methods from File::Find::Rule # take useful things from File::Find::Rule use base 'File::Find::Rule'; Force your madness into the main package # and force our crack into the main namespace sub File::Find::Rule::random () { my $self = shift()->_force_object; $self->exec( sub { rand > 0.5 } ); } Yes, we're being very cavalier here and defining things into the main File::Find::Rule namespace. This is due to lack of imaginiation on my part - I simply can't find a way for the functional and oo interface to work without doing this or some kind of inheritance, and inheritance stops you using two File::Find::Rule::Foo modules together. For this reason try and pick distinct names for your extensions. If this becomes a problem then I may institute a semi-official registry of taken names. Taking no arguments. Note the null prototype on random. This is a cheat for the procedural interface to know that your sub takes no arguments, and so allows this to happen: find( random => in => '.' ); If you hadn't declared "random" with a null prototype it would have consumed "in" as a parameter to it, then got all confused as it doesn't know about a '.' rule. AUTHOR
Richard Clamp <richardc@unixbeard.net> COPYRIGHT
Copyright (C) 2002 Richard Clamp. All Rights Reserved. This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
File::Find::Rule File::Find::Rule::MMagic was the first extension module, so maybe check that out. perl v5.18.2 2011-09-19 File::Find::Rule::Extending(3)
All times are GMT -4. The time now is 05:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy