Description of problem: At one time in history, the "-l" option on the "df" command worked fine even when some NFS mounted filesystems were not talking (because, for instance, the remote system is down or troubled in some way). Now, df issues a stat() for every dadgum mountpoint, even when called with the -l option. If an NFS mount is having trouble this can hang forever (with the right mount options). The whole point of -l was to avoid this (well, a major point, anyway). Version-Release number of selected component (if applicable): coreutils-8.21-21.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1.run strace df -l -h on a system with network mounts. 2.grep the strace output for stat() calls. 3.see stat() calls for every single network mount as well as the local ones. Actual results: Hang when there is network or server trouble Expected results: No hang, it shouldn't be touching anything on the network. Additional info: Here are some of the stat() calls from my fedora 20 system at work. All these names are NFS mountpoints, yet I ran with the -l option: stat("/trex/tooth", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/userland", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/raptor/fang", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/ada/denmark", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/raptor/foot", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/varmit/stew", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/tt/sulphur", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/marmot/burrow", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/marmot/fur", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/raptor/bite", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/tt/hydrogen", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/raptor/claw", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 stat("/iggy/pop", {st_mode=S_IFDIR|0777, st_size=4096, ...}) = 0 stat("/tt/carbon", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
This is a fair point, and probably wound up in another change I'm looking at to avoid needing to stat to get device IDs. I'll take a look upstream
Fix proposed upstream http://lists.gnu.org/archive/html/coreutils/2015-04/msg00009.html
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.