[lkml]   [1998]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why a find causes a flush? wrote:

> I wonder why doing a "find /some_dir" causes the kernel to mark buffers
> as dirty so the next scheduled flush writes these buffers out to disk.
> I haven't taken any look at the code but I see how the dcache saves
> accesses to disk when doing the find, but I can also see how the disk
> is accessed about 2 seconds after find finishes, or when sync is run.

The find command updates the directory access times, so the associated
buffers get flushed to disk at the next interval.

This is normal behavior, but there's a NODIRATIME option if you don't want
the access times to be updated.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:43    [W:0.028 / U:19.616 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site