My early flush patch will fix this, or at least it will if I get
together with the ReiserFS guys and figure out how to integrate their
flushing mechanism with the standard bdflush. Or they could
incorporate the ideas from my early flush in their own flush daemon,
though generalizing the standard flush would have more value in the
> The '<file>~' that Emacs makes is usually fine though.
Because it's "created" by a rename.
> Once, I lost power in on my SQL box, [it was blessedly during a
> period of no use.] I had to rebuild all the indexes. Not only
> THAT, but what happens to that box if I lose power whilst in the
> middle of operations? I am working on the migration plan to move that
> to XFS because of these concerns. [However, I am doing a better job
> of testing with XFS first.]
Help is on its way. You can try full-data journalling with the journal
on NVRAM or on a separate disk. You can also wait for me to get a
usable version of Tux2 working. It's progressed a little slowly
because of frequent side trips ;-) But hopefully I'll be able to do
something about that soon.
Which flavor of SQL are you using? Are the indices in separate files?
(Sounds like they are.)
> I think that Reiser is cool, and has neat ideology, but I am
> un-nerved by this behaviour.
I think it's not hard to fix.
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/