From: Hisashi Hifumi <hifumi.hisashi@oss.ntt.co.jp>
To: Zach Brown <zach.brown@oracle.com>,
Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH] dio: falling through to buffered I/O when invalidationof a page fails
Date: Mon, 17 Dec 2007 11:38:45 +0900 [thread overview]
Message-ID: <6.0.0.20.2.20071217111426.03956ca8@172.19.0.2> (raw)
In-Reply-To: <4762D651.50801@oracle.com>
At 04:15 07/12/15, Zach Brown wrote:
>
>> If anyone has a testcase - I can take a look at the problem again.
>
>I can try and throw something together..
>
>- z
I did a test by using fsstress.
I modified the dio write() of fsstress to check return value, and input
following command;
# fsstress -d /root/testdir/ -l 0 -n 1000 -p 1000 -z -f creat=1 -f write=1
-f dwrite=1
I got EIO from dio write.
I encountered some PostgreSQL mailing list archive that mentioned about
this issue.
http://groups.google.com/group/pgsql.hackers/browse_thread/thread/c7515ccd5ac1269c/dc2ddeac3fe0d8c1?lnk=raot&fwc=1
dio can be used in PostgreSQL to write transaction log(WAL). It is said
that when dio is used,
EIO is returned under some workload.
prev parent reply other threads:[~2007-12-17 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 7:52 [PATCH] dio: falling through to buffered I/O when invalidation of a page fails Hisashi Hifumi
2007-12-12 1:00 ` Zach Brown
2007-12-12 7:51 ` [PATCH] dio: falling through to buffered I/O when invalidationof " Hisashi Hifumi
2007-12-14 18:59 ` [PATCH] dio: falling through to buffered I/O when invalidation of " Badari Pulavarty
2007-12-14 19:15 ` Zach Brown
2007-12-17 2:38 ` Hisashi Hifumi [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=6.0.0.20.2.20071217111426.03956ca8@172.19.0.2 \
--to=hifumi.hisashi@oss.ntt.co.jp \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=zach.brown@oracle.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 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).