From: Jens Benecke <jens@jensbenecke.de>
To: linux-kernel@vger.kernel.org,
Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: [reiserfs-list] Re: ReiserFS data corruption in very simple configuration
Date: Mon, 24 Sep 2001 11:25:10 +0200 [thread overview]
Message-ID: <20010924112510.F15955@jensbenecke.de> (raw)
In-Reply-To: <200109221000.GAA11263@out-of-band.media.mit.edu> <15276.34915.301069.643178@beta.reiserfs.com>
In-Reply-To: <15276.34915.301069.643178@beta.reiserfs.com>; from Nikita@Namesys.COM on Sat, Sep 22, 2001 at 04:47:31PM +0400
[-- Attachment #1: Type: text/plain, Size: 1474 bytes --]
On Sat, Sep 22, 2001 at 04:47:31PM +0400, Nikita Danilov wrote:
> foner-reiserfs@media.mit.edu writes:
> > [Please CC me on any replies; I'm not on linux-kernel.]
> >
> > The ReiserFS that comes with both Mandrake 7.2 and 8.0 has
> > demonstrated a serious data corruption problem, and I'd like to know
> > (a) if anyone else has seen this, (b) how to avoid it, and (c) how to
> > determine how badly I've been bitten.
> >
> Stock reiserfs only provides meta-data journalling. It guarantees that
> structure of you file-system will be correct after journal replay, not
> content of a files. It will never "trash" file that wasn't accessed at
> the moment of crash, though. Full data-journaling comes at cost. There is
> patch by Chris Mason <Mason@Suse.COM> to support data journaling in
> reiserfs. Ext3 supports it also.
one question:
When I was using ext2 I always mounted the /usr partition read-only, so
that a fsck weren't necessary at boot - and the files were all guaranteed
to be OK to bring the system up at least.
Does this (mount -o ro) make sense with ReiserFS as well? What I mean is,
is there a chance of a file getting corrupted that was only *read* (not
*written*) at or before a power outage?
I mount all my system partitions with -o notail,noatime if that makes any
difference.
--
Jens Benecke ········ http://www.hitchhikers.de/ - Europas Mitfahrzentrale
rm -rf /bin/laden
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next prev parent reply other threads:[~2001-10-14 13:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-22 10:00 ReiserFS data corruption in very simple configuration foner-reiserfs
2001-09-22 12:47 ` Nikita Danilov
2001-09-22 20:44 ` foner-reiserfs
2001-09-25 13:28 ` Stephen C. Tweedie
2001-09-29 4:44 ` Lenny Foner
2001-09-29 12:52 ` [reiserfs-list] " Lehmann
2001-10-01 1:00 ` foner-reiserfs
2001-10-01 1:26 ` Lehmann
2001-10-01 2:32 ` foner-reiserfs
2001-10-03 16:28 ` Toby Dickenson
2001-10-01 11:30 ` Stephen C. Tweedie
2001-09-24 9:25 ` Jens Benecke [this message]
2001-10-14 14:52 ` [reiserfs-list] " Chris Mason
2001-10-14 18:19 ` Jens Benecke
2001-10-14 20:04 ` Hans Reiser
2001-10-14 23:32 ` Bernd Eckenfels
2001-09-25 20:13 ` Mike Fedyk
2001-09-26 14:43 ` Stephen C. Tweedie
2001-10-01 3:38 ` Mike Fedyk
2001-10-03 16:14 ` Stephen C. Tweedie
2001-10-01 15:27 ` Hans Reiser
2001-10-03 16:17 ` Stephen C. Tweedie
2001-10-03 20:06 ` Pascal Schmidt
2001-10-04 11:02 ` Stephen C. Tweedie
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=20010924112510.F15955@jensbenecke.de \
--to=jens@jensbenecke.de \
--cc=Reiserfs-List@namesys.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