From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8941] New: "ls" of an NFSv4 share only works when pumped through strace
Date: Wed, 18 May 2016 20:24:56 +0000 [thread overview]
Message-ID: <bug-8941-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=8941
Bug ID: 8941
Summary: "ls" of an NFSv4 share only works when pumped through
strace
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: stevejhorton at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Buildroot = Nightly build commit (46f9454ae177f309c226f4cb8fe7b7f68a109b29)
nfs-utils = 1.3.3
busybox = 1.24.1 also tried 1.24.2
Network = 10 Gigabit Ethernet on all hosts
I'm placing the bug here because I can't tell if it's a buildroot or a busybox
issue.
NOTES: With a good NFS mount from a buildroot image I can not see the file
names unless I use strace like so.
------------------------
# ls -la /share/FILES # I get nothing
# strace -o /dev/null ls -la /share/FILES/
total 44
drwxrwxrwx 4 42949672 42949672 4096 Apr 4 15:58 .
drwxrwxrwx 1045 42949672 42949672 32768 May 18 20:03 ..
drwxrwxrwx 2 42949672 42949672 4096 May 18 15:05 dir1
drwxrwxrwx 2 42949672 42949672 4096 Apr 4 15:58 dir2
# nfsstat -m
/share from server:/lab/1
Flags:
rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=14,retrans=2,sec=sys,clientaddr=10.10.50.230,local_lock=none,addr=10.10.90.10
#
Any Ideas?
Many Thanks!
-S
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-05-18 20:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 20:24 bugzilla at busybox.net [this message]
2016-10-15 15:37 ` [Buildroot] [Bug 8941] "ls" of an NFSv4 share only works when pumped through strace bugzilla at busybox.net
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=bug-8941-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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