Sponsored Content
Full Discussion: tcpdump - stealing storage
Top Forums UNIX for Dummies Questions & Answers tcpdump - stealing storage Post 302503655 by truecall on Friday 11th of March 2011 08:45:18 AM
Old 03-11-2011
tcpdump - stealing storage

Hello,

I hope someone can explain something to me just so I can understand why this took place:

We have Avaya telephony servers that are running RHEL 5 on them. A week ago, callers were dialing into the server and could not hear a ".wav" file that was supposed to be played in an AVP IVR. Not real important.

Come to find out, the / mount was out of storage. The strange thing was nothing really was adding up. I performed the df and du commands. I also performed the find command with the size flags to see if there were some large log files . . . nothing really showed up that was large. The / mount btw was 20 Gigs.

While doing a ps aux command I saw some tcpdumps taking place (over a year ago). It was piping the output to the tmp directory. I looked and these traces were NOT in the tmp directory.

Once I killed the processes, the storage came back!!!!

I just was hoping that someone could tell me where these files were at because I sure didn't see them. I can only assume that the trace was taking place, then an admin forgot to kill them. Then maybe some /tmp cleanup job removed the files but had I not performed the ps aux command I would have never known about this.

I understand that a reboot would have absolutely fixed this problem, but I hate to reboot unless absolutely necessary.

Thanks for sheding light on this. Linux is a learning experience for me every day and I always learn something valuable from these forums!

Tim.
 

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Starting a program without it stealing focus

Hi all I have a java program I'm starting in Mac os from the terminal using the command java -Djava.library.path=/Users/me/Desktop/Cfiles/DynamicCTGLayout/build/Release -jar However, when I do this, my current program I'm using becomes "deselected" and the java program's GUI becomes... (2 Replies)
Discussion started by: WhiteTiger
2 Replies

2. UNIX for Dummies Questions & Answers

Display command stealing focus

Please Help a Newbie, I'm using the display command to post a picture of several configurations for a machine operator to choose from. The Issue I have is when I display the image the displayed image steals focus from my bash window. The operator then has to re-select the window to answer the... (1 Reply)
Discussion started by: BitBoy
1 Replies
lofs(7FS)							   File Systems 							 lofs(7FS)

NAME
lofs - loopback virtual file system SYNOPSIS
#include <sys/param.h> #include <sys/mount.h> int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0); DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys- tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or until the corresponding mount point in the virtual file system is covered by a file system mounted there. virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options; the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are inherited from the underlying file systems. A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot, including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories. Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a process or family of processes. Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed (for example, as an empty directory). Examples lofs file systems are mounted using: mount -F lofs /tmp /mnt SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D) WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. A loopback mount entry in /etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop- back mount entry the last in /etc/vfstab. SunOS 5.10 10 Apr 2001 lofs(7FS)
All times are GMT -4. The time now is 06:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy