emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#16539: closed (df command, possible bug?)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16539: closed (df command, possible bug?)
Date: Fri, 24 Jan 2014 22:28:02 +0000

Your message dated Fri, 24 Jan 2014 23:27:11 +0100
with message-id <address@hidden>
and subject line Re: bug#16539: More details on df command output for you
has caused the debbugs.gnu.org bug report #16539,
regarding df command, possible bug?
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16539: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16539
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: df command, possible bug? Date: Fri, 24 Jan 2014 15:23:02 -0500 User-agent: Roundcube Webmail/0.8.4


The df command as distributed with OpenSuSE 13.1 -- package coreutils-8.21-7.8.1.x86_64 does not return all currently mounted nfs mounts when specifying the command with no command line arguments. Specifying the df command: df -at nfs works perfectly and
returns the data for all mounted nfs filesystems.

uname -a output for your reference:
Linux otw-l0 3.11.6-4-desktop #1 SMP PREEMPT Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) x86_64 x86_64 x86_64 GNU/Linux

If you need further information please let me know.

Thank you,

Curtis

--
Curtis Rubel
Senior Development Engineer
Compro Computer Services, Inc.
105 East Drive - Melbourne, Florida, 32904
Phone: 321-727-2211
email: address@hidden
Web: http://www.compro.net

"An ISO 9001:2008 Registered Company"



--- End Message ---
--- Begin Message --- Subject: Re: bug#16539: More details on df command output for you Date: Fri, 24 Jan 2014 23:27:11 +0100 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
tag 16539 notabug
close
thanks

On 01/24/2014 09:47 PM, Curtis Rubel wrote:
> 
> df command output with no args:
> 
> only 1 nfs mount is listed
> 
> address@hidden:~> df
> Filesystem          1K-blocks     Used Available Use% Mounted on
> /dev/sda3           173232952 44850568 127310032  27% /
> devtmpfs              4049732       32   4049700   1% /dev
> tmpfs                 4095336       76   4095260   1% /dev/shm
> tmpfs                 4095336     4688   4090648   1% /run
> tmpfs                 4095336        0   4095336   0% /sys/fs/cgroup
> tmpfs                 4095336     4688   4090648   1% /var/run
> tmpfs                 4095336     4688   4090648   1% /var/lock
> /dev/sda1             1035084    45272    920848   5% /boot
> host:/usr/local/bin 110217536 40202928  68990448  37% /usr/local/muse
> address@hidden:~>
> 
> 
> df command with options to show nfs mounted filesystems
> showing all nfs mounts.
> 
> address@hidden:~> df -at nfs
> Filesystem                  1K-blocks     Used Available Use% Mounted 
> on
> host:/usr/local/muse        110217536 40203472  68989896  37% 
> /usr/local/muse
> host:/usr/local/LINUX_FILES 110217536 40203472  68989896  37% 
> /usr/local/LINUX_FILES
> host:/usr/local/3rdparty    110217536 40203472  68989896  37% 
> /usr/local/3rdparty
> address@hidden:~>

Just for info: df in openSUSE-13.1 is currently identical to that
in coreutils-v8.21.

The above is the result of df suppressing duplicate entries like
bind mounts.  This filtering is done based on the device number.
As this example shows, a few exports of directories of the same file
system from "host" are mounted - yet it's the same file system.

We already had a few discussions about this filtering of duplicate
mount entries. For me, this example shows that the current implementation
is not that bad because df's job is to show block and inode usage
statistics about mounted file systems.  When it comes to information
about mount points, then I think findmnt(1) from util-linux is
the right tool.

I'm therefore tagging this bug as "notabug" and mark it as done.
If you or someone else wants to continue this discussion, then
this can of course be done in this thread. And if someone has
the *golden* idea how to solve this problem, then just stand up
and let use know.

Have a nice day,
Berny


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]