On Mon, Oct 14, 2002 at 09:20:27AM +0200, Harald Staub wrote: > This is probably stupid, but I am quite happy with the following > "solution". I hacked the source. The 5 second commit interval is hardcoded > in > > fs/jbd/journal.c: > > journal->j_commit_interval = (HZ * 5); > > I changed 5 to 300. What I think this means is that I may loose 5 minutes > of work, which is acceptible for me, but crash recovery is fast. Since I
In recent kernel (2.4.20pre...), an option (commit) is available. > have crashes only when experimenting with the kernel, I think this is not > as bad as it might look at first glance. But, you know, no guarantees of > mine, your filesystem might become garbled, your hard disk might become > fried! In my opinion this is not a solution. First I am still not convinced that it is normal for ext3 to touch the disk when there is no other activity on the system. Then spinning the disk for 5 minutes seems very bad from the powersaving point of view and also from the life of the HD. That said if you have done nothing else, I am not sure if your disk enter in a powersaving state. Have you tweaked it with hdparm or are you using noflushd? Christophe > Harry > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] -- Christophe Barbé <[EMAIL PROTECTED]> GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E A qui sait comprendre, peu de mots suffisent. (Intelligenti pauca.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
