corrupted: kmailrc contains html code ?!

[Simon Hausmann]

On Mon, Jul 22, 2002 at 10:25:54AM +0400, Vadim Plessky wrote:
> On Sunday 21 July 2002 2:46 pm, Martijn Klingens wrote:
> |  On Sunday 21 July 2002 11:52, Rolf Magnus wrote:
> |  > Do you by any chance use reiserfs? It tends to write "strange stuff"
> |  > into files on a system crash.
> |
> |  That's not very special for reiserfs.
> |
> |  On non-journaling file-systems you can only pray the file data and the
> |  meta-data are in sync. fsck will find most of it, but you can still have a
> |  problem like this if you're unlucky.
> |
> |  And all journaling file systems that write the meta data before the actual
> |  file data have this problem, which means pretty much all of them. IIRC
> | only ext3 can be configured to write metadata after the write, which is
> | slower but more safe. ext3 can even be told to write the file data (!) to
> | the journal, causing 100% correct replays of transactions. Needless to see
> | that's terribly slow, and ext3 already was slower for partitions with lots
> | of small files than reiserfs...
> |
> |  In general it's a tradeoff between performance and 100% data security
> | whether to pick reiser or ext3. For most applications reiser is already far
> | more reliable than any non-journaling system out there.
> 
> So, what journaling file system you recommend for running KDE?
> May be, JFS or XFS is a better option than ReiserFS or Ext3?

Neither journalling filesytem prevents you from possible data
corruption in case of a crash, except ext3's data journalling. But
enabling that is bound to a huge performance loss.

Simon