Messages in this thread | | | Date | Tue, 04 Jun 2002 12:21:20 +0100 | From | Padraig Brady <> | Subject | Re: Need help tracing regular write activity in 5 s interval |
| |
Matthias Andree wrote: > Hello, > > I am using some recent Linux 2.4.x version (2.4.19-pre8-ac5 for now), > and I have been observing regular disk activity at 5 s intervals for > some time now which are not related to a particular kernel version. > > I have reiserfs and ext3fs file systems mounted. > > The first thing that came to mind with the "5 s interval" was DJB's > "svscan", but neither mount -o remount,noatime / nor killall -STOP > svscan helped. > > The next thing that comes to mind is that journalling file systems > commit their journal every five seconds. But I have a hard time finding > out which file system does this or which process causes blocks to be > marked dirty again. I'd really like to get rid of this regular activity > unless there's a need. > > So: is there any trace software that can tell me "at 15:52:43.012345, > process 4321 marked 7 blocks dirty on device /dev/hda5" (or even more > detail so I can figure if it's just an atime update -- as with svscan -- > or a write access)? And that is NOT to be attached to a specific process > (hint: strace is not an option). > > Also, I'd like to suggest again a mount option that marks filesystems as > "clean" automatically after all changes have been committed. This may be > most useful with "noatime", though. > > Thanks in advance, >
This thread may be of interest: http://marc.theaimsgroup.com/?l=linux-kernel&m=101600745431992&w=2
It's very awkward to analyse things like this at present. For user -> kernel you could use something like syscalltrack.
As an aside, Nautilus (1.0.4) does stuff every 2 seconds (checking is there a CD inserted) that causes the disk LED to flash. The same action also causes the kernel (2.4.13) to fill up the ring buffer with: "VFS: Disk change detected on device ide1(22,0)".
Padraig.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |