Return-Path: linux-nfs-owner@vger.kernel.org
Received: from mail-vc0-f172.google.com ([209.85.220.172]:58239 "EHLO
	mail-vc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S934096AbaGPOrO (ORCPT
	<rfc822;linux-nfs@vger.kernel.org>); Wed, 16 Jul 2014 10:47:14 -0400
Received: by mail-vc0-f172.google.com with SMTP id im17so1887677vcb.3
        for <linux-nfs@vger.kernel.org>; Wed, 16 Jul 2014 07:47:13 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CALtMJEDT=jCWMR0Akjo72fL3SW63dEmDTQbdg5Pv_DV5Oggz_g@mail.gmail.com>
References: <CALtMJECmW-yYgD3W5FUxQZJVZkb5NSJpQ5V9Q3ZE=1NKeCDtOA@mail.gmail.com>
	<20140710175136.GA26561@fieldses.org>
	<CALtMJECLdEOsmuW4AOnNsAyY+OMr3MtFN9W71DRw3tpidKrU8A@mail.gmail.com>
	<CAHQdGtQAgKyFgwp+6w64vXkcKkBQ=YVfiH0jgaonAMumHoTutg@mail.gmail.com>
	<CALtMJEDT=jCWMR0Akjo72fL3SW63dEmDTQbdg5Pv_DV5Oggz_g@mail.gmail.com>
Date: Wed, 16 Jul 2014 07:47:13 -0700
Message-ID: <CAHQdGtS_O3i6fBhW7vTurL=Y7cKmoeGjTXiEMU5mbb3tR3-LjA@mail.gmail.com>
Subject: Re: `ls` shows no files in mounted nfs folder, but ls 'file' works
From: Trond Myklebust <trond.myklebust@primarydata.com>
To: Andreas Fenkart <afenkart@gmail.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
        Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
        Daniel Mack <zonque@gmail.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-nfs-owner@vger.kernel.org
List-ID: <linux-nfs.vger.kernel.org>

On Wed, Jul 16, 2014 at 1:21 AM, Andreas Fenkart <afenkart@gmail.com> wrote:
> 2014-07-16 1:54 GMT+02:00 Trond Myklebust <trond.myklebust@primarydata.com>:
>> On Sun, Jul 13, 2014 at 11:44 PM, Andreas Fenkart <afenkart@gmail.com> wrote:
>>> 2014-07-10 19:51 GMT+02:00 J. Bruce Fields <bfields@fieldses.org>:
>>>> On Mon, Jun 23, 2014 at 12:07:22PM +0200, Andreas Fenkart wrote:
>>>>> Found regression introduced by this patch
>>>>>
>>>>> 311324ad NFS: Be more aggressive in using readdirplus for 'ls -l' situations"
>>>>>
>>>>> # cd /bin
>>>>> -sh: cd: /bin: Not a directory
>>>>> root@192:/# pwd
>>>>> /
>>>>> root@192:/# ls /bin
>>>>> ls: /bin
>>>>> root@192:/# ls -l /bin/sh
>>>>> lrwxrwxrwx    1 root     root             9 Jun 16 13:59 /bin/sh -> /bin/bash
>>>>>
>>>>> the mount options of the client, an embedded system, mounting nfsroot:
>>>>> nfs(rw,relatime,vers=2,rsize=4096,wsize=4096,namlen=255,hard,nolock,proto=udp,timeo=11,retrans=3,sec=sys,mountaddr=192.168.xx.xx,mountvers=1,mountproto=udp,local_lock=all,addr=192.168.xx.xx)
>>>>> vers: 3.16.0-rc1
>>>>>
>>>>> the server exports:
>>>>> /exports/rootfs 192.168.xx.xx(rw,no_root_squash,subtree_check)
>>>>> vers: 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64 GNU/Linux
>>>>>
>>>>> reverting above patch, dir listing with 'ls /' works again
>>>>
>>>> Is this still happening?
>>>
>>> yes it is, I just reverted the aforementioned commit.
>>
>> Can you reapply, and then do an "ls /" while recording the traffic to
>> the NFS server using wireshark, and then send us the resulting dump?
>
> http://www.pcapr.net/view/afenkart/2014/6/3/1/nfs-client.dump.html
> you have to create a login... simple. Or did you mean attach to email?
>
>> If the client is on an embedded system which can't run wireshark, then
>> it is fine to record it on the server, but please use something like
>>
>> 'tshark -w /var/tmp/dump.out host <client-ip>'
>
> captured on embedded system:
> tcpdump -w /tmp/nfs-client.dump
>
>>
>> Cheers
>>   Trond
>
> thanks, sincerely
> Andreas

That unfortunately only shows a few READ requests, probably because
the readdirs etc are cached. Could you try again with a directory that
is not in cache and/or try "echo 3 >/proc/sys/vm/drop_caches" before
retrying the 'ls /'?

Note: I am a little surprised that there are no GETATTRs in that dump.
Even if the readdir is cached, the client is supposed to revalidate
the directory.

-- 
Trond Myklebust

Linux NFS client maintainer, PrimaryData

trond.myklebust@primarydata.com