> I wrote the fs/buffer.c changes in 2.2.8 that are causing so many
> problems. I'm debugging as fast as I can. Here are some notes.
What about just reversing the patch for 2.2.9? Was there bug in
bdflush? I though we are in feature freeze!
> 1. Don't run update with 2.2.8. It's unnecessary and it's causing
> filesystem corruption for some people. This has to be a bug somewhere
> else in the kernel; update is simply calling sync() every thirty
> seconds.
<SARCASTIC MODE ON>Great news, tell that to 10M users out there
:-(. You may even post slashdot message "everybody go and upgrade to
2.2.8, it screws up filesystems".</SARCASTIC>
> 2. If you want your disks to spin down, try mounting filesystems with
> noatime. I do not like the idea of postponing writes indefinitely at
> all.
You don't like idea of postponing writes indefinitely and suggest me
to break my system with noatime. I like idea of postponing writes
until sync is given. That is legal and it is definitely less breakage
of unix semantics than noatime.
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 Please read the FAQ at http://www.tux.org/lkml/