From: Chris Mason <mason@suse.com>
To: berthiaume_wayne@emc.com
Cc: reiserfs-list@namesys.com, manuel.krause@mb.tu-ilmenau.de
Subject: RE: [PATCH CFT] tons of logging patches
Date: 04 Jun 2002 12:55:28 -0400 [thread overview]
Message-ID: <1023209728.31683.170.camel@tiny> (raw)
In-Reply-To: <93F527C91A6ED411AFE10050040665D0049BFAF9@corpusmx1.us.dg.com>
On Tue, 2002-06-04 at 11:48, berthiaume_wayne@emc.com wrote:
> Chris, isn't there a danger, remotely, that with data=ordered you
> could lose your data? For Ext3FS, if the machine should crash after the
> filesystem data is updated but before the metadata is updated, fsck(8) will
> reclaim the newly allocated blocks; therefore, the updated file is no longer
> correct.
Yes, reiserfs does the same. data=ordered only promises that before the
updated metadata is on disk, the data blocks they reference will be on
disk too. This way you know that if you add new bytes to a file, after
a crash you will either have valid data in the file, or no new bytes
added at all.
The only way you can be sure the actual metadata is there is by waiting
for an fsync(file) to finish.
-chris
next prev parent reply other threads:[~2002-06-04 16:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 15:48 [PATCH CFT] tons of logging patches berthiaume_wayne
2002-06-04 16:55 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-14 0:52 Manuel Krause
2002-08-02 12:28 ` Chris Mason
2002-06-22 20:02 Dieter Nützel
2002-06-24 19:05 ` Chris Mason
2002-07-09 13:52 ` Dieter Nützel
2002-07-09 14:00 ` Chris Mason
2002-06-03 3:51 Chris Mason
2002-06-03 4:04 ` Chris Mason
2002-06-03 8:46 ` Matthias Andree
2002-06-03 12:26 ` Chris Mason
2002-06-04 0:45 ` Manuel Krause
2002-06-04 1:49 ` Manuel Krause
2002-06-04 2:20 ` Chris Mason
2002-06-04 3:28 ` Manuel Krause
2002-06-04 13:12 ` Chris Mason
2002-06-05 21:13 ` Manuel Krause
2002-06-05 21:27 ` Manuel Krause
2002-06-05 21:32 ` Chris Mason
2002-06-06 0:09 ` Chris Mason
2002-06-12 22:32 ` Manuel Krause
2002-06-17 0:47 ` Chris Mason
2002-06-17 0:31 ` Manuel Krause
2002-06-17 19:04 ` Chris Mason
2002-06-21 0:25 ` Chris Mason
2002-06-28 13:51 ` Chris Mason
2002-07-02 18:16 ` Chris Mason
2002-07-03 20:56 ` Chris Mason
2002-07-04 0:28 ` Manuel Krause
2002-07-08 13:51 ` Chris Mason
2002-06-04 2:57 ` Chris Mason
2002-06-04 4:16 ` Manuel Krause
2002-06-04 13:34 ` Chris Mason
2002-06-04 21:20 ` Hans Reiser
2002-06-05 0:16 ` Robert Brockway
2002-06-05 8:43 ` Oleg Drokin
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=1023209728.31683.170.camel@tiny \
--to=mason@suse.com \
--cc=berthiaume_wayne@emc.com \
--cc=manuel.krause@mb.tu-ilmenau.de \
--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.