Messages in this thread | | | Date | Sun, 26 Mar 2006 08:14:48 +0100 | From | "Benoit Boissinot" <> | Subject | Re: Connector: Filesystem Events Connector v3 |
| |
On 25 Mar 2006 18:16:32 -0500, Greg Stark <gsstark@mit.edu> wrote: > > yang.y.yi@gmail.com writes: > > > the filesystem events connector is small and has low overhead, it only > > focuses on activities in the filesystem, so I think it should be an option > > for those users which just concerns events in the filesystem. audit dose do > > this, but it is complicated and overhead is big, I believe the filesystem > > events connector is useful, but it maybe need to be improved further. > > Would this be a good tool to tell me why I hear my hard drive stutter > periodically? This is above the regular buffer flushing. > > I'm curious what application is causing this file i/o since I have plenty of > free RAM so the only reason it would be hitting disk is if something is > calling fsync gratuitously. > blktrace (included at least in -mm) will tell you.
You have to activate BLK_DEV_IO_TRACE and use blktrace from http://www.kernel.org/pub/linux/kernel/people/axboe/blktrace/
regards,
Benoit - 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/
| |