Skip to contentSkip to conversation

New: "ls" of an NFSv4 share only works when pumped through strace

Buildroot bugzilla at busybox.net 1 participant 2 messages May 18, 2016 – Oct 15, 2016

lore
Share & tools
lore
#0 lore 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

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 8941] "ls" of an NFSv4 share only works when pumped through strace

https://bugs.busybox.net/show_bug.cgi?id=8941

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |WONTFIX

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Thanks for your bug report, and sorry for the slow response.

Unfortunately, this doesn't really look like a Buildroot problem, but most likely a kernel problem.

Can you test the same kernel, with another distribution (like a Debian distribution) ? Which C library are you using ? If you're using uClibc, can you try glibc ? Is it happening with a different hardware platform, like if you boot the Buildroot system under Qemu ?

We would really need you to investigate further this bug.

Alternatively, you could provide a detailed step-by-step process on how to reproduce the bug: a minimal Buildroot Qemu based defconfig that exhibits the problem, together with the details on how to setup a NFSv4 server. As it is, it's too much effort to setup everything that's needed to reproduce your bug.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.