From: Andrew Morton <akpm@zip.com.au>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_DIRECT fails in some kernel and FS
Date: Fri, 01 Feb 2002 12:44:29 -0800 [thread overview]
Message-ID: <3C5AFE2D.95A3C02E@zip.com.au> (raw)
In-Reply-To: <E16WkQj-0005By-00@antoli.uib.es>
Ricardo Galli wrote:
>
> After some comments from Oliver Diedrich (editor of heise.de), which told me
> he couldn't make O_DIRECT work on 2.4.17, I tried with different versions and
> file systems:
>
> This is the result:
>
> 2.4.14 - Ext[23] - redhat7.2 glibs: OK (at least the bytes are written)
> 2.4.17 - ReiserFS - Debian Sid : FAILS (0 bytes file, write returns -1)
> 2.4.17 - Ext2 - Debian Woody : OK (bytes written)
> 2.4.17 - Ext3 - Debian Woody : FAILS (0 bytes file, write returns -1)
>
> Oliver Diedrich also told he could make work O_DIRECT with ext3 and 2.4.17.
>
> Is this normal? Does it really work on 2.4.14? Or it doesn't but the kernel
> doesn't avoid caching?
>
ext2 is the only filesystem which has O_DIRECT support.
-
next prev parent reply other threads:[~2002-02-01 20:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 20:37 O_DIRECT fails in some kernel and FS Ricardo Galli
2002-02-01 20:44 ` Andrew Morton [this message]
2002-02-01 20:49 ` Ricardo Galli
2002-02-01 20:57 ` Andrew Morton
2002-02-01 21:05 ` Steve Lord
2002-02-02 9:35 ` Chris Wedgwood
2002-02-02 10:25 ` Hans Reiser
2002-02-02 15:24 ` Chris Mason
2002-02-02 18:20 ` Chris Mason
2002-02-02 19:54 ` Andrea Arcangeli
2002-02-02 20:10 ` Chris Mason
2002-02-02 20:16 ` Stephen Lord
2002-02-02 20:50 ` Jeff Garzik
2002-02-03 13:40 ` Stephen Lord
2002-02-03 14:09 ` Chris Wedgwood
2002-02-03 15:05 ` Stephen Lord
2002-02-03 22:44 ` Chris Wedgwood
2002-02-04 15:04 ` Jeff Garzik
2002-02-04 15:21 ` Chris Mason
2002-02-04 15:15 ` Steve Lord
2002-02-04 15:46 ` Alan Cox
2002-02-04 16:02 ` Steve Lord
2002-02-04 18:22 ` Daniel Phillips
2002-02-04 19:11 ` Steve Lord
2002-02-04 18:29 ` Joel Becker
2002-02-04 18:49 ` Jeff Garzik
2002-02-04 18:55 ` Joel Becker
2002-02-04 19:16 ` Jeff Garzik
2002-02-02 17:14 ` Christoph Hellwig
[not found] <E16WkQj-0005By-00@antoli.uib.es.suse.lists.linux.kernel>
[not found] ` <3C5AFE2D.95A3C02E@zip.com.au.suse.lists.linux.kernel>
[not found] ` <1012597538.26363.443.camel@jen.americas.sgi.com.suse.lists.linux.kernel>
[not found] ` <20020202093554.GA7207@tapu.f00f.org.suse.lists.linux.kernel>
[not found] ` <234710000.1012674008@tiny.suse.lists.linux.kernel>
[not found] ` <20020202205438.D3807@athlon.random.suse.lists.linux.kernel>
[not found] ` <242700000.1012680610@tiny.suse.lists.linux.kernel>
[not found] ` <3C5C4929.5080403@sgi.com.suse.lists.linux.kernel>
[not found] ` <20020202155028.B26147@havoc.gtf.org.suse.lists.linux.kernel>
2002-02-03 7:26 ` Andi Kleen
2002-02-04 15:13 ` Jeff Garzik
2002-02-04 15:31 ` Chris Mason
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=3C5AFE2D.95A3C02E@zip.com.au \
--to=akpm@zip.com.au \
--cc=gallir@uib.es \
--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