From: Chuck Lever <chuck.lever@oracle.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: Correct behavior on O_DIRECT sparse file writes
Date: Mon, 15 Oct 2007 11:36:18 -0400 [thread overview]
Message-ID: <471388F2.8010605@oracle.com> (raw)
In-Reply-To: <871wbzp88o.fsf@mid.deneb.enyo.de>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Florian Weimer wrote:
> * Andrew Morton:
>
>> I don't think it's a bug. Sure, O_DIRECT is synchronous, but that's
>> because it is, err, direct. Not because it provides extra data-integrity
>> guarantees. If you want those guarantees, use O_SYNC as well.
>
> This needs to be prominently documented. Right now, it's far from clear
> that you need both O_DIRECT and O_SYNC.
It's certainly not a requirement for NFS. O_DIRECT on NFS forces data
to the server, which always updates a file's metadata on each write,
including indirect blocks.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 259 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
version:2.1
end:vcard
next prev parent reply other threads:[~2007-10-15 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 20:39 Correct behavior on O_DIRECT sparse file writes Chris Mason
2007-10-12 21:02 ` Andrew Morton
2007-10-13 11:24 ` Florian Weimer
2007-10-15 15:36 ` Chuck Lever [this message]
2007-10-15 16:53 ` Bryan Henderson
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=471388F2.8010605@oracle.com \
--to=chuck.lever@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=fw@deneb.enyo.de \
--cc=linux-fsdevel@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.