From: Kristian Nielsen <knielsen@knielsen-hq.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ext3/4] PROBLEM: fdatasync not syncing appended data (w/test program)
Date: Tue, 04 Sep 2012 08:07:25 +0200 [thread overview]
Message-ID: <87mx165nj6.fsf@frigg.knielsen-hq.org> (raw)
In-Reply-To: <20120903135756.GI21109@quack.suse.cz> (Jan Kara's message of "Mon, 3 Sep 2012 15:57:56 +0200")
Jan Kara <jack@suse.cz> writes:
> On Mon 03-09-12 10:45:15, Kristian Nielsen wrote:
>> It appears that ext3 and ext4 fdatasync() does not fully sync data to
>> disk. Specifically, when new data is written at the end (so that the file
>> length is increased), not all of the new data is synced by fdatasync().
> The culprit is that we forget to update i_datasync_tid when we change only
> inode size. Thus inode is not forced to disk during fdatasync(). I will send
> fixes for this in a moment.
Cool, thanks for the quick response! Glad that we get this fixed.
- Kristian.
prev parent reply other threads:[~2012-09-04 6:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 8:45 [ext3/4] PROBLEM: fdatasync not syncing appended data (w/test program) Kristian Nielsen
2012-09-03 13:57 ` Jan Kara
2012-09-04 6:07 ` Kristian Nielsen [this message]
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=87mx165nj6.fsf@frigg.knielsen-hq.org \
--to=knielsen@knielsen-hq.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).