After lots of testing, I can say that 2.5.18 works great in all three
modes of ext3 for all but one purpose. Oracle database still gets
corrupted during insert load. More precisely, online redo log gets
corrupted, database panics and restore is in order.
This leads me to thinking that there's something wrong with sysv
shared memory in 2.5.x. Although the problem could also be in fsync()
or swap_out() & co. paths, it's yet to be discovered.
It could also be that journaled mode helps the trouble, and it could
be that some swapping makes it more certain, but none of these two
facts are proved for sure. Take it as an observation.
Christoph, I don't know if you're still taking care of shmem in 2.5.x,
so take my apologies if you didn't want to see this email.
Regards,
-- Zlatko - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/