From: Hans Reiser <reiser@namesys.com>
To: Jens Benecke <jens@jensbenecke.de>
Cc: 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, 15 Oct 2001 00:04:39 +0400 [thread overview]
Message-ID: <3BC9EFD7.D014C9C7@namesys.com> (raw)
In-Reply-To: <200109221000.GAA11263@out-of-band.media.mit.edu> <15276.34915.301069.643178@beta.reiserfs.com> <20010924112510.F15955@jensbenecke.de> <2143070000.1003071174@tiny> <20011014201907.H20001@jensbenecke.de>
Jens Benecke wrote:
> What I meant is this: AFAIK, if you exclude broken hardware, in ext2 there
> is no chance of a file that was never written to since mounting being
> corrupted on a crash, even if the fs was mounted read-write.
>
> Is this the same thing with ReiserFS?
Yes.
next prev parent reply other threads:[~2001-10-14 20:04 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 ` [reiserfs-list] " Jens Benecke
2001-10-14 14:52 ` Chris Mason
2001-10-14 18:19 ` Jens Benecke
2001-10-14 20:04 ` Hans Reiser [this message]
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=3BC9EFD7.D014C9C7@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=jens@jensbenecke.de \
--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