On Mon, 28 Sep 1998 15:08:29 -0700, "D.A. Harris"
<rodmur@ecst.csuchico.edu> said:
> Hopefully this is just simple problem, but I just did an upgrade from
> 2.1.115 to 2.1.122, and now when I reboot, / is busy and not unmouting
> cleanly. Could this be a problem with the kernel?
This is a FAQ. Older kernels did not complain if you tried to remount
as readonly a filesystem which had orphaned (deleted but still open)
files present. They should have done so, and current kernels do.
The problem is most often caused by mmap()s of /etc/ld.so.cache left
around by glibc: if you do an ldconfig, then old processes such as init
will still be left with an open handle onto the old version of
ld.so.cache. The latest versions of glibc-2.0.7 unmap this file after
loading to deal more appropriately with the fixed kernel behaviour.
> also do we need "update (bdflush)" daemon once there is a "(kflushd)"
> kernel thread running?
Yes. update is a daemon triggered to write out dirty data after a
certain amount of time. kflushd is there to trickle dirty buffers out
if the kernel is running out of memory internally. Correct operation
needs both. This is also a FAQ!
--Stephen
-
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.tux.org/lkml/