From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] fallocate vs O_(D)SYNC
Date: Wed, 16 Nov 2011 03:42:56 -0500 [thread overview]
Message-ID: <20111116084256.GA22963@infradead.org> (raw)
It seems all filesystems but XFS ignore O_SYNC for fallocate, and never
make sure the size update transaction made it to disk.
Given that a fallocate without FALLOC_FL_KEEP_SIZE very much is a data
operation (it adds new blocks that return zeroes) that seems like a
fairly nasty surprise for O_SYNC users.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
mfasheh@suse.com, jlbec@evilplan.org, cluster-devel@redhat.com
Subject: fallocate vs O_(D)SYNC
Date: Wed, 16 Nov 2011 03:42:56 -0500 [thread overview]
Message-ID: <20111116084256.GA22963@infradead.org> (raw)
It seems all filesystems but XFS ignore O_SYNC for fallocate, and never
make sure the size update transaction made it to disk.
Given that a fallocate without FALLOC_FL_KEEP_SIZE very much is a data
operation (it adds new blocks that return zeroes) that seems like a
fairly nasty surprise for O_SYNC users.
next reply other threads:[~2011-11-16 8:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 8:42 Christoph Hellwig [this message]
2011-11-16 8:42 ` fallocate vs O_(D)SYNC Christoph Hellwig
2011-11-16 9:43 ` [Cluster-devel] " Steven Whitehouse
2011-11-16 9:43 ` Steven Whitehouse
2011-11-16 10:54 ` Jan Kara
2011-11-16 10:54 ` Jan Kara
2011-11-16 11:20 ` Steven Whitehouse
2011-11-16 11:20 ` Steven Whitehouse
2011-11-16 12:45 ` Christoph Hellwig
2011-11-16 12:45 ` Christoph Hellwig
2011-11-16 13:39 ` Jan Kara
2011-11-16 13:39 ` Jan Kara
2011-11-16 13:42 ` Christoph Hellwig
2011-11-16 13:42 ` Christoph Hellwig
2011-11-16 15:57 ` Jan Kara
2011-11-16 15:57 ` Jan Kara
2011-11-16 16:16 ` Christoph Hellwig
2011-11-16 16:16 ` Christoph Hellwig
2011-11-16 16:18 ` Chris Mason
2011-11-16 19:35 ` Mark Fasheh
2011-11-16 20:03 ` Mark Fasheh
2011-11-16 20:03 ` Mark Fasheh
2011-11-17 10:16 ` Joel Becker
2011-11-17 10:16 ` Joel Becker
2011-11-18 12:09 ` [Cluster-devel] " Steven Whitehouse
2011-11-18 12:09 ` Steven Whitehouse
2011-11-16 11:28 ` Zheng Liu
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=20111116084256.GA22963@infradead.org \
--to=hch@infradead.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.