On 25 Mar 2006 18:16:32 -0500, Greg Stark <[email protected]> wrote:
>
> [email protected] 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
