From: Steve Dickson <SteveD-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Andrew Holway <a.holway-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org>
Cc: kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
libvir-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: NFS over RDMA small block DIRECT_IO bug
Date: Tue, 11 Sep 2012 13:03:37 -0400 [thread overview]
Message-ID: <504F6EE9.5070908@RedHat.com> (raw)
In-Reply-To: <F416961E-A33A-44D3-A788-5EF598A0AAFE-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org>
On 09/04/2012 05:31 AM, Andrew Holway wrote:
> Hello.
>
> # Avi Kivity avi(a)redhat recommended I copy kvm in on this. It would also seem relevent to libvirt. #
>
> I have a Centos 6.2 server and Centos 6.2 client.
>
> [root@store ~]# cat /etc/exports
> /dev/shm 10.149.0.0/16(rw,fsid=1,no_root_squash,insecure) (I have tried with non tempfs targets also)
>
>
> [root@node001 ~]# cat /etc/fstab
> store.ibnet:/dev/shm /mnt nfs rdma,port=2050,defaults 0 0
>
>
> I wrote a little for loop one liner that dd'd the centos net install image to a file called 'hello' then checksummed that file. Each iteration uses a different block size.
>
> Non DIRECT_IO seems to work fine. DIRECT_IO with 512byte, 1K and 2K block sizes get corrupted.
>
> I want to run my KVM guests on top of NFS over RDMA. My guests cannot create filesystems.
>
> Thanks,
>
> Andrew.
>
> bug report: https://bugzilla.linux-nfs.org/show_bug.cgi?id=228
Well it appears the RHEL6 kernels are lacking a couple patches that might
help with this....
5c635e09 RPCRDMA: Fix FRMR registration/invalidate handling.
9b78145c xprtrdma: Remove assumption that each segment is <= PAGE_SIZE
I can only image that Centos 6.2 might me lacking these too... ;-)
steved.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-11 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:31 NFS over RDMA small block DIRECT_IO bug Andrew Holway
[not found] ` <F416961E-A33A-44D3-A788-5EF598A0AAFE-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org>
2012-09-04 12:04 ` Myklebust, Trond
2012-09-04 12:52 ` Andrew Holway
[not found] ` <4FA345DA4F4AE44899BD2B03EEEC2FA908F82C6C-VGJ86jkg8PeBTCzCEi1xmXOR4cbS7gtM96Bgd4bDwmQ@public.gmane.org>
2012-09-05 14:02 ` Avi Kivity
2012-09-06 10:14 ` Andrew Holway
[not found] ` <6F777077-D7FC-4F51-8806-C89A5F973DFA-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org>
2012-09-06 13:45 ` Myklebust, Trond
2012-09-11 17:03 ` Steve Dickson [this message]
[not found] ` <504F6EE9.5070908-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2012-09-18 14:03 ` Andrew Holway
[not found] ` <72D13AE7-98F6-4582-9C64-66AAEE0BB4D8-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org>
2012-09-19 15:50 ` Steve Dickson
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=504F6EE9.5070908@RedHat.com \
--to=steved-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=a.holway-V6oZj8nR2NRn68oJJulU0Q@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=libvir-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).