Created attachment 1225 [details] Buildroot configuration I set up a very basic root filesystem with large file support (BR2_LARGEFILE=y) using Buildroot. But ls from both Busybox and Coreutils fails on large directories. In my case /mnt, which is a 1.4TB cifs share. On a smaller(~100GB) one it works fine. Strace shows that ls fires fstat() instead of fstat64(). So I wore a small testtool, which uses the fstat() library call. It worked perfectly. According to strace my tool uses fstat64(). It seems that Buildroot messes something up while building Busybox and Coreutils with large file support. Config files, strace logs and my testtool are attached. I reproduced this issue with Buildroot 2010.02 and snapshot from yesterday.
Created attachment 1231 [details] Busybox configuration (generated)
Created attachment 1237 [details] uClibc config (generated)
Created attachment 1243 [details] strace busybox's ls
Created attachment 1249 [details] strace coreutils's ls
Created attachment 1255 [details] strace testtool
Created attachment 1261 [details] the testtool
Working just fine with qemu_x86_defconfig + LARGEFILE + cifs-utils + strace (and tweaked kernel with CONFIG_CIFS=m against a 2 TB share). Strace shows busybox ls using *stat64 all along. Didn't try coreutils ls but i guess this was fixed along some time ago because of the bug age.