08-17-2013
Why do you suspect a process holding a file open when your list is empty?
If there are open files, there must be process(es) on the local side holding the files open; it might be children (or so) of the NFS daemon. Did you check the NFS log files?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello ,
I want to get current system open file table value. Can any one help.
Thanking you,
mahesh (0 Replies)
Discussion started by: mahesh.
0 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I have here a hard drive from a computer that was damaged, and now the costumer needs the data on the hard drive, but doesn't have any other computer to read data.
I don't really know what file system is on the disk.
How can I find out what file system is on the disk so I can read the... (4 Replies)
Discussion started by: dmarques
4 Replies
3. UNIX for Dummies Questions & Answers
Hi,
when I run sfdisk -l get:
Disk /dev/sda: 19452 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 12 13- 104391 83 Linux... (1 Reply)
Discussion started by: mojoman
1 Replies
4. Solaris
Hi Experts,
I was asked to find most busy file system on one of the server. It is Sun 10. Any idea to get this?
Thanks,
Deepak (5 Replies)
Discussion started by: naw_deepak
5 Replies
5. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
6. UNIX for Advanced & Expert Users
Is there some way to tell what processes are attached to a shared memory segment? We have a system on which I perform "icps -ma" and there are several segments pending deletion having numerous processes attached to them and I can't tell what processes they are. Neither the creator's pid nor last... (7 Replies)
Discussion started by: DreamWarrior
7 Replies
7. Shell Programming and Scripting
When I run 'top' command,I see the following
Memory: 32G real, 12G free, 96G swap free
Though it shows as 12G free,I am not able to account for processes that consume the rest 20G.
In my understanding some process should be consuming atleast 15-16 G but I am not able to find them.
Is... (1 Reply)
Discussion started by: prasperl
1 Replies
8. Shell Programming and Scripting
The end result that I'd like is to terminate any process on my ps -u username list that extends beyond 20 minutes. I know for a fact that this process will be named l.exe, but I don't know the number in between and I won't know the PID. Is there a way to use grep or pidof to do this task every 20... (2 Replies)
Discussion started by: Bolanok
2 Replies
9. UNIX for Dummies Questions & Answers
Platform: Oracle Linux 6.4
To find the most memory consuming processes, I tried the following 2 methods
1. Method1
# ps aux | head -1 ; ps aux | sort -nk +4 | tail -7
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 95 0.0 0.0 0 0 ? ... (2 Replies)
Discussion started by: kraljic
2 Replies
10. Solaris
Hi all,
q1) If i am in a global-zone, is there any command or anyway to check if a particular process in "ps -ef" output is running in which zone ?
q2) if i have created and mount a lofs filesystem/mountpoint for my non-global zone, can i say the following
e.g.
/dev/md/dsk/d60 /data --... (1 Reply)
Discussion started by: javanoob
1 Replies
fsx(8) System Manager's Manual fsx(8)
NAME
fsx - file system exerciser
SYNOPSIS
/usr/field/fsx [-h] [-ofile] [-tn] [-fpath] [-pm]
OPTIONS
The fsx options are: Prints the help messages for the fsx command. Saves the output diagnostics in file. Run time in minutes (n). The
default is to run until the process receives a Ctrl/C or a kill -15 pid command. Number (m) of fsx processes to spawn. The maximum is 250;
the default is 20. Path name of directory on file system you wish to test. For example, /mnt or /usr. The default is /usr/field.
DESCRIPTION
The fsx exerciser spawns the background process fsxr, and these two processes exercise a file system by creating, opening, writing, open-
ing, reading, validating, closing, and unlinking a test file. These test files are created in the /usr/field directory (the default)
unless the -fpath option is used.
You can spawn up to 250 (default is 20) fsx processes (fsxr1, fsxr2, ... fsxrn where n is the number of processes spawned). The exerciser
will run until a Ctrl/C or kill -15 pid command is sent to the process.
A logfile for you to examine and then remove is created in the current working directory. If there are errors in the logfile, make sure you
check the syslog file where the driver and kernel error messages are saved.
RESTRICTIONS
If you must run a system exerciser over an NFS link or on a diskless system, there are some restrictions. For exercisers such as fsx(8),
which must write into a file system, the target file system must be writable by root. Also, the directory in which any of the exercisers
are executed must be writable by root because temporary files are written into the current directory. These latter restrictions are some-
times difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of the
restrictions may be overcome by copying fsx and fsxr to another directory and then executing it. Avoid using the fsx exerciser over an NFS
or diskless file system.
Each time you run fsx, it creates a log file. The exerciser allows you to accumulate up to 9 log files. If you run fsx to create a tenth
log file, it exits and displays the following error messages:
fsx: Remove old log files fsx: Can not start report generator, test aborted
When this situation occurs, remove at least one log file and run fsx again.
EXAMPLES
The following example runs 10 fsx processes on /mnt until the process receives a Ctrl/C or kill -15 pid command: % /usr/field/fsx -p10
-f/mnt The following example runs 20 fsx processes on /usr/field for 120 minutes in the background: % /usr/field/fsx -t120 &
SEE ALSO
Commands: cmx(8), diskx(8), memx(8), shmx(8), tapex(8)
fsx(8)