All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kaspar <zkaspar82@gmail.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4 O_DIRECT with 3.16.2 kernel issue (qemu kvm cache=none / RHEL5 guest)
Date: Mon, 06 Oct 2014 17:18:25 +0200	[thread overview]
Message-ID: <5432B2C1.7090901@gmail.com> (raw)
In-Reply-To: <CAHQdGtRVfNQs7bBDbY8yH2Fzq3MyFyBBxbuTDH63w6WTqs4zPQ@mail.gmail.com>

On 09/12/2014 06:31 PM, Trond Myklebust wrote:
> On Fri, Sep 12, 2014 at 12:23 PM, Zdenek Kaspar <zkaspar82@gmail.com> wrote:
>> 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.
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> Don't use 3.16.x kernels with NFS yet. There are known bugs in the
> read/write code that need a stable backport of a set of fixes that are
> in 3.17-rc.
> 
> 

Hi Trond, noticed big nfs update that got into -stable, running 3.16.4
on both sides and problem is fixed, thx!

Z.

  reply	other threads:[~2014-10-06 15:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 16:23 NFSv4 O_DIRECT with 3.16.2 kernel issue (qemu kvm cache=none / RHEL5 guest) Zdenek Kaspar
2014-09-12 16:31 ` Trond Myklebust
2014-10-06 15:18   ` Zdenek Kaspar [this message]
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=5432B2C1.7090901@gmail.com \
    --to=zkaspar82@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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 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.