From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: gurudas pai <gurudas.pai@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] nfs: readv/writev with O_DIRECT fails on 2.6.24-rc1
Date: Mon, 29 Oct 2007 15:59:37 -0400 [thread overview]
Message-ID: <1193687977.7497.45.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <47258C0A.2040603@oracle.com>
On Mon, 2007-10-29 at 13:00 +0530, gurudas pai wrote:
> Hi,
>
> While running olt kit on 2.6.24-rc1 over nfs , Oracle reported I/O
> errors. I debugged little more and found that readv/writev are failing
> with O_DIRECT on nfs ( netapp's filer).
>
> I am able to re-produce same error using ltp/diotest5.
>
> ./diotest5 -f /storage/nas/testfile -v 5
>
> diotest05 1953719669 FAIL : readv failed: Invalid argument
> diotest05 1953719670 FAIL : Read with Direct IO, Write without
> diotest05 1953719671 FAIL : writev failed: Invalid argument
> diotest05 1953719672 FAIL : Write with Direct IO, Read without
> diotest05 1953719673 FAIL : writev failed: Invalid argument
> diotest05 1953719674 FAIL : Read, Write with Direct IO
> diotest05 0 INFO : 3/3 testblocks failed
>
> >strace -e readv,writev ./diotest5 -f /storage/nas/testfile -v 5
> writev(3, [{"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}], 5) = 20480
> readv(4, 0x8051000, 5) = -1 EINVAL (Invalid argument)
> diotest05 1953719669 FAIL : readv failed: Invalid argument
> diotest05 1953719670 FAIL : Read with Direct IO, Write without
> writev(3, [{"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}], 5) = -1 EINVAL(Invalid argument)
> diotest05 1953719671 FAIL : writev failed: Invalid argument
> diotest05 1953719672 FAIL : Write with Direct IO, Read without
> writev(3, [{"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}, {"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 4096}], 5) = -1 EINVAL(Invalid argument)
> diotest05 1953719673 FAIL : writev failed: Invalid argument
> diotest05 1953719674 FAIL : Read, Write with Direct IO
> diotest05 0 INFO : 3/3 testblocks failed
> Process 4749 detached
>
>
> mount options:
> rw,bg,nointr,hard,timeo=600,wsize=32768,rsize=32768,nfsvers=3,tcp,actimeo=0
>
>
> Please let me know if I have to try test/debug patch.
Nobody has yet added support for nvec>1.
Trond
next prev parent reply other threads:[~2007-10-29 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 7:30 gurudas pai
2007-10-29 19:59 ` Trond Myklebust [this message]
2007-10-30 6:52 ` Gurudas Pai
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=1193687977.7497.45.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=gurudas.pai@oracle.com \
--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
all inboxes | Powered by JetHome®