From: Sam Vilain <sam@vilain.net>
To: Oleg Drokin <green@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Data corrupted after crash
Date: Fri, 26 Jul 2002 14:44:05 +0100 [thread overview]
Message-ID: <20020726134405.D4DB145B@hofmann> (raw)
In-Reply-To: <20020726131943.A18706@namesys.com>
Oleg Drokin <green@namesys.com> wrote:
> No. Reiserfs provides only metadata journaling. So the data itself still
> may be damaged (data still may be damaged even in case of full data
> journaling just because there is no API for applications to control
> transactions currently)
Still, data journalling would be nice. I must say that when reiserfs gets
the power taken out from under it, you don't half end up with your
recently worked on files containing pieces of each other.
With data journalling, this would not be a problem; although of course
files could end up in a half-updated state, which to a given application
may as well be corrupted. It would be a bit slower, unless your journal is on a seperate device, but that can't be helped.
--
Sam Vilain, sam@vilain.net WWW:
http://sam.vilain.net/ 7D74 2A09 B2D3 C30F F78E GPG:
http://sam.vilain.net/sam.asc 278A A425 30A9 05B5 2F13
You've one mouth and two ears...use them in that proportion.
- anon.
next prev parent reply other threads:[~2002-07-26 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 17:54 Data corrupted after crash Sebastian Kaps
2002-07-26 9:19 ` Oleg Drokin
2002-07-26 9:34 ` Sebastian Kaps
2002-07-26 13:44 ` Sam Vilain [this message]
2002-07-26 13:53 ` Oleg Drokin
2002-07-26 15:17 ` Chris Mason
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=20020726134405.D4DB145B@hofmann \
--to=sam@vilain.net \
--cc=green@namesys.com \
--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.