> Statistics only confuse the issue. Disks are only mounted/unmounted
Agreed.
My idea: Last time I checked, linux was not guaranteeing that all data
are on disk after sync. Sync just means that data are scheduled in que
somewhere. So you have to sleep 1 after sync, for it to work.
But that is wrong. You should sleep_until_all_data_are written. But
this is impossible as you don't know it. 1sec was just guess.
I _think_ that there's something similar going on with unmount.
Is it possible that similar issue is here? Could you please try
recompiling w/o swap _AND_ w/o update? That should produce lots of
unsaved data. Also watch disk activity few msec before machine is
physically reset.
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu