I played with a new 128MB RAM machine and by mistake the machine got
resetted before umounting a filesystems. The following fsck managed
to delete lots of files, including near all changes on the filesystem of
the last 15 minutes or so.
In these 15 minutes the disk nor the CPU were busy so the kernel
should have had enough time to write out the dirty pages.
I've never seen these problems, even with 2.1 kernels, on machines with
less memory (32MB, 64MB), although I often have kernel crashes when I do
driver development.
It seems bdflush doesn't do enough to write out dirty pages when there
is no memory pressure. I think that is a bug and should be fixed.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu