From: Troy Benjegerdes <hozer@drgw.net>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Emmanuel Varagnat <Emmanuel_Varagnat-AEV010@email.mot.com>,
linux-kernel@vger.kernel.org
Subject: Re: ReiserFS file corruption
Date: Tue, 7 Aug 2001 13:28:26 -0500 [thread overview]
Message-ID: <20010807132826.T17468@altus.drgw.net> (raw)
In-Reply-To: <3B6E84A1.1A13969@crm.mot.com> <3B6E8A09.ABCDAFFC@redhat.com>
In-Reply-To: <3B6E8A09.ABCDAFFC@redhat.com>; from arjanv@redhat.com on Mon, Aug 06, 2001 at 01:14:02PM +0100
On Mon, Aug 06, 2001 at 01:14:02PM +0100, Arjan van de Ven wrote:
> Emmanuel Varagnat wrote:
> >
> > Today, I crashed the kernel and after reboot the source file
> > I was working on, was completly unreadable. The size indicated
> > by 'ls' seems to be good but with bad data.
>
> Well reiserfs doesn't guarantee the CONTENTS of the file to be
> consistent after a crash; only the metadata.
Hrrrm, maybe the following change (or something like it) would be good
for Documentation/Configure.help
===== Configure.help 1.46 vs edited =====
--- 1.46/Documentation/Configure.help Sat Aug 4 11:40:39 2001
+++ edited/Configure.help Tue Aug 7 13:27:41 2001
@@ -11706,7 +11706,12 @@
CONFIG_REISERFS_FS
Stores not just filenames but the files themselves in a balanced
- tree. Uses journaling.
+ tree. Currently uses metatdata-only journaling.
+
+ (NOTE: metadata-only journalling only ensures the filesystem is
+ consistent after a crash, NOT the data! You need data AND metadata
+ journaling to guarantee open files do not get corrupted on a crash.
+ full data journalling is also slower.)
Balanced trees are more efficient than traditional
filesystem architectural foundations.
next prev parent reply other threads:[~2001-08-07 18:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-06 11:50 Emmanuel Varagnat
2001-08-06 12:04 ` Rasmus Bøg Hansen
2001-08-06 12:13 ` bvermeul
2001-08-06 12:14 ` Arjan van de Ven
2001-08-07 18:28 ` Troy Benjegerdes [this message]
2001-08-07 19:02 ` Hans Reiser
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=20010807132826.T17468@altus.drgw.net \
--to=hozer@drgw.net \
--cc=Emmanuel_Varagnat-AEV010@email.mot.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®