From: matoro via GNU coreutils Bug Reports <bug-coreutils@gnu.org>
To: 64123@debbugs.gnu.org
Subject: bug#64123: "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS
Date: Fri, 16 Jun 2023 19:55:41 -0400 [thread overview]
Message-ID: <5281da6ac0e7d97e27b539e58c8bef1e@matoro.tk> (raw)
Hi, when running the command "stat -f -c '%T' ." on an alpha while being
on an NFS filesystem, the command fails with EOVERFLOW.
$ stat -f -c "%T" .
stat: cannot read file system information for '.': Value too large for
defined data type
The command does NOT fail when targeting any other filesystem type.
$ stat -f -c "%T" /
ext2/ext3
I 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!
next reply other threads:[~2023-06-17 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 23:55 matoro via GNU coreutils Bug Reports [this message]
2023-06-17 17:30 ` bug#64123: "stat -f -c '%T' ." on alpha fails with EOVERFLOW with NFS Pádraig Brady
2023-06-17 19:23 ` Paul Eggert
2023-06-17 19:53 ` matoro via GNU coreutils Bug Reports
2023-06-17 22:19 ` Pádraig Brady
2023-06-18 1:26 ` Paul Eggert
2023-06-20 6:29 ` Paul Eggert
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
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5281da6ac0e7d97e27b539e58c8bef1e@matoro.tk \
--to=bug-coreutils@gnu.org \
--cc=64123@debbugs.gnu.org \
--cc=matoro_mailinglist_bug-coreutils@matoro.tk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).