All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Mayrhuber <christian.mayrhuber@gmx.net>
To: Menno Smits <menno@netbox.biz>
Cc: reiserfs-list@namesys.com
Subject: Re: Repeatable corruption using Reiserfs 3
Date: Thu, 30 Oct 2003 14:02:12 +0100	[thread overview]
Message-ID: <3FA10BD4.6040800@gmx.net> (raw)
In-Reply-To: <3FA0A9D9.70705@netbox.biz>

Menno Smits wrote:

> - The result is expected and correct. Now look at the tail of the files.
>   The results vary on every run of the test but the contents of the
>   output files are always wrong. Two examples are:
This behaviour is completely correct. Reiserfs V3 does only meta data
journaling by default, which means, that file metadata operations like 
create, delete, etc. are journaled, but not the actual data written to 
the disk.

If you want to prevent data corruption on power failure and not just 
filesystem corruption you have to use Chris Mason's data logging 
patches, see ftp://ftp.suse.com/pub/people/mason/patches/data-logging
These patches provide an additional mount option:
data=writeback: Metadata journaling only
data=ordered: (new default) Data is written to disk before a metadata
               transaction is commited to journal. (nearly as fast as
               writeback, protects against data corruption)
data=journal: Data and metadata are commited to journal and then written
               to disk. (slower, except for mail servers)

-- 
lg, Chris


      parent reply	other threads:[~2003-10-30 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30  6:04 Repeatable corruption using Reiserfs 3 Menno Smits
2003-10-30 11:57 ` Hans Reiser
2003-10-30 13:02 ` Christian Mayrhuber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FA10BD4.6040800@gmx.net \
    --to=christian.mayrhuber@gmx.net \
    --cc=menno@netbox.biz \
    --cc=reiserfs-list@namesys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.