From: "J. Bruce Fields" <bfields@fieldses.org>
To: Andreas Fenkart <afenkart@gmail.com>
Cc: rond Myklebust <trond.myklebust@primarydata.com>,
linux-nfs@vger.kernel.org, Daniel Mack <zonque@gmail.com>
Subject: Re: `ls` shows no files in mounted nfs folder, but ls 'file' works
Date: Thu, 10 Jul 2014 13:51:36 -0400 [thread overview]
Message-ID: <20140710175136.GA26561@fieldses.org> (raw)
In-Reply-To: <CALtMJECmW-yYgD3W5FUxQZJVZkb5NSJpQ5V9Q3ZE=1NKeCDtOA@mail.gmail.com>
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, dirlisting with 'ls /' works again
Is this still happening?
--b.
next prev parent reply other threads:[~2014-07-10 17:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 10:07 `ls` shows no files in mounted nfs folder, but ls 'file' works Andreas Fenkart
2014-07-10 17:51 ` J. Bruce Fields [this message]
2014-07-14 6:44 ` Andreas Fenkart
2014-07-15 23:54 ` Trond Myklebust
2014-07-16 8:21 ` Andreas Fenkart
2014-07-16 14:47 ` Trond Myklebust
2014-07-16 15:45 ` Andreas Fenkart
2014-07-25 22:12 ` Trond Myklebust
2014-08-26 19:50 ` J. Bruce Fields
2014-08-27 8:30 ` Andreas Fenkart
2014-08-27 13:26 ` J. Bruce Fields
2014-08-28 7:42 ` Andreas Fenkart
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=20140710175136.GA26561@fieldses.org \
--to=bfields@fieldses.org \
--cc=afenkart@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=zonque@gmail.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.