From: Zdenek Kaspar <zkaspar82@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: NFSv4 O_DIRECT with 3.16.2 kernel issue (qemu kvm cache=none / RHEL5 guest)
Date: Fri, 12 Sep 2014 18:23:26 +0200 [thread overview]
Message-ID: <54131DFE.9020708@gmail.com> (raw)
Hello everyone, got this specific problem with RHEL5 guest under KVM
hypervisor.
client/server kernel version: 3.16.2
/etc/exports: rw,async,no_subtree_check,no_root_squash
/proc/mounts: nfs4 rw,relatime,vers=4.0,rsize=524288,wsize=524288,
namlen=255,hard,proto=tcp,port=0,
timeo=600,retrans=2,sec=sys,clientaddr=xxx.xxx.xxx.xxx,
local_lock=none,addr=xxx.xxx.xxx.yyy 0 0
CONFIG_NFS_FS=m
# CONFIG_NFS_V2 is not set
CONFIG_NFS_V3=m
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=m
# CONFIG_NFS_SWAP is not set
# CONFIG_NFS_V4_1 is not set
# CONFIG_NFS_USE_LEGACY_DNS is not set
CONFIG_NFS_USE_KERNEL_DNS=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
# CONFIG_NFSD_V3_ACL is not set
CONFIG_NFSD_V4=y
# CONFIG_NFSD_FAULT_INJECTION is not set
CONFIG_NFS_COMMON=y
CentOS-5.10-i386-bin-1of8.iso -- did not test everything on centos,
behaved same as RHEL5. So let's use it as VM reproducer:
dd if=/dev/zero of=kvm-test1.img bs=1M count=2048
start VM using:
file=kvm-test1.img,cache=writeback,aio=native,if=virtio,boot=on
create custom layout: /dev/vda1 / ext3 max size primary
unselect Desktop-Gnome, select Customize now
use only: Base System/Base and install it..
[root@test1 ~]# find / >/dev/null
everything works as expected with writeback
shutdown, backup kvm-test1.img (fs will explode)
start VM using:
file=kvm-test1.img,cache=none,aio=native,if=virtio,boot=on
[root@test1 ~]# find / >/dev/null
and check dmesg, reboot etc, ie:
EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in
directory #460317: rec_len is smaller than minimal - offset=0, inode=0,
rec_len=0, name_len=0
EXT3-fs error (device vda1): htree_dirblock_to_tree: bad entry in
directory #98503: rec_len is smaller than minimal - offset=0, inode=0,
rec_len=0, name_len=0
Tested locally on ext4, xfs - WORK
Tested on NFSv4 share with ext4, xfs - FAIL
Tested NFSv4 share sync, async - FAIL
Tested on NFSv3 share with xfs - WORK
KVM with qemu rhel-6.5, 2.1.1 - SAME RESULTS
NOTE: it seems just the rhel5 guest triggers it easily..
HTH, Z.
next reply other threads:[~2014-09-12 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 16:23 Zdenek Kaspar [this message]
2014-09-12 16:31 ` NFSv4 O_DIRECT with 3.16.2 kernel issue (qemu kvm cache=none / RHEL5 guest) Trond Myklebust
2014-10-06 15:18 ` Zdenek Kaspar
2014-10-06 15:19 ` Trond Myklebust
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=54131DFE.9020708@gmail.com \
--to=zkaspar82@gmail.com \
--cc=linux-nfs@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.