|
From: | GNU bug Tracking System |
Subject: | bug#64123: closed ("stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS) |
Date: | Tue, 20 Jun 2023 06:30:01 +0000 |
Your message dated Mon, 19 Jun 2023 23:29:06 -0700 with message-id <3cd04b41-3253-e873-6daa-bf52e3380477@cs.ucla.edu> and subject line Re: bug#64123: "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS has caused the debbugs.gnu.org bug report #64123, regarding "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 64123: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64123 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS Hi, when running the command "stat -f -c '%T' ." on an alpha while being on an NFS filesystem, the command fails with EOVERFLOW. Date: Fri, 16 Jun 2023 19:55:41 -0400 $ stat -f -c "%T" .stat: cannot read file system information for '.': Value too large for defined data typeThe command does NOT fail when targeting any other filesystem type. $ stat -f -c "%T" / ext2/ext3I am aware that EOVERFLOW is typically associated with 32-bit systems failing to hold 64-bit inodes and such. However, alpha is a pure 64-bit system; there does not even exist a 32-bit version.This is the only platform on which I have observed this behavior. I also checked on all other platforms, including x86, arm, ppc, riscv, mips, sparc, hppa, and ia64. No other platform exhibited this error.I am using kernel 6.3, glibc 2.37, and coreutils 9.3. If anybody would mind taking a look at this bug, I can provide direct shell access to the machine in question, with strace etc installed. Thank you!
--- End Message ---
--- Begin Message ---Subject: Re: bug#64123: "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS Date: Mon, 19 Jun 2023 23:29:06 -0700 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 On 2023-06-17 12:53, matoro via GNU coreutils Bug Reports wrote:Compiling with -D_FILE_OFFSET_BITS=64 fixes the problem.Thanks for checking. I installed the following fix to coreutils: https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=5ac7f2d281ef70500fc70211dc1f146c8666e8c1 This incorporates the following Gnulib fix: https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=f4919b224dd1545190f35eb481f78694f2337cb1 which is derived from the following Autoconf fix: https://git.savannah.gnu.org/cgit/autoconf.git/commit/?id=103514e40da5f20aebf83a3446452ccebe5172bbwhich should cause 'configure' to #define _FILE_OFFSET_BITS to 64 on GNU/Linux s390x and alpha.Closing the coreutils bug report.
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |