From: "Stephen C. Tweedie" <sct@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Re: ReiserFS data corruption in very simple configuration
Date: Wed, 3 Oct 2001 17:14:51 +0100 [thread overview]
Message-ID: <20011003171451.A5209@redhat.com> (raw)
In-Reply-To: <200109221000.GAA11263@out-of-band.media.mit.edu> <15276.34915.301069.643178@beta.reiserfs.com> <20010925131304.I23320@mikef-linux.matchmail.com> <20010926154311.C12560@redhat.com> <20010930203831.A25387@mikef-linux.matchmail.com>
In-Reply-To: <20010930203831.A25387@mikef-linux.matchmail.com>; from mfedyk@matchmail.com on Sun, Sep 30, 2001 at 08:38:31PM -0700
Hi,
On Sun, Sep 30, 2001 at 08:38:31PM -0700, Mike Fedyk wrote:
> >From what you're describing, it looks like the contents of test after a
> truncate won't be overwritten by another transaction until the deletion of
> those blocks has made it to disk... So, while in ordered, or journal mode,
> I'd end up with "a" in test, but with writeback mode there is no such
> guarantee.
>
> Am I missing something?
>
> Are there any known cases where ext3 will not be able to recover pervious
> data when a write wasn't able to complete?
It depends on what the application is doing. Applications often open
an existing file with O_TRUNC, write to it, then close it. If you
crash between the truncate and the write being committed, then you'll
get a perfectly legal, sane, consistent, empty file on recovery.
--Stephen
next prev parent reply other threads:[~2001-10-03 16:14 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
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 [this message]
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=20011003171451.A5209@redhat.com \
--to=sct@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 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.