Messages in this thread | | | From | peloy@ven ... | Subject | Re: Why a find causes a flush? | Date | 10 Aug 1998 16:01:24 GMT |
| |
Thanks guys, everything is understood now. Now I know why the noatime mount option is so useful.
Regards,
peloy.-
Bill Hawes <whawes@transmeta.com> wrote: > peloy@ven.ra.rockwell.com 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. > > Regards, > Bill > > >
--
Eloy A. Paris Information Technology Department Rockwell Automation Venezuela Telephone: +58-2-9432311 Fax: +58-2-9431645
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
| |