Description of problem: The default output of "df" is getting more and more confusing. It displays lots of mounts that are just "technical" and have nothing to do with disk free space. Here is the output on my system: Filesystem Size Used Avail Use% Mounted on rootfs 7.6G 132M 7.1G 2% / devtmpfs 2.0G 0 2.0G 0% /dev tmpfs 2.0G 1.9M 2.0G 1% /dev/shm tmpfs 2.0G 912K 2.0G 1% /run /dev/sda1 7.6G 132M 7.1G 2% / /dev/sda6 20G 9.4G 9.2G 51% /usr tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup tmpfs 2.0G 1.8M 2.0G 1% /tmp /dev/sda7 20G 561M 18G 3% /var /dev/sda8 6.7G 16M 6.3G 1% /usr/local /dev/sda9 16G 266M 16G 2% /home /dev/sda1 7.6G 132M 7.1G 2% /var/lib/named/etc/named.conf /dev/sda1 7.6G 132M 7.1G 2% /var/lib/named/etc/rndc.key /dev/sda1 7.6G 132M 7.1G 2% /var/lib/named/etc/named.iscdlv.key /dev/sda1 7.6G 132M 7.1G 2% /var/lib/named/etc/named.root.key /dev/sda6 20G 9.4G 9.2G 51% /var/lib/named/usr/lib64/bind /dev/sda6 20G 9.4G 9.2G 51% /var/lib/named/usr/lib64/openssl /dev/sda7 20G 561M 18G 3% /var/lib/named/var/named As you can see, the last 7 lines are "bind" mounts done for the DNS server. They should not be seen. The root ("/") is shown twice. Most the tmpfs outputs do not really help either. One thing to clean it up is to do the default alias like df -h -x tmpfs -x rootfs -x devtmpfs -x supermount Unfortunately, it still shows bind mounts and this seems to require the change to the "df" itself. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
CC: (none) => mageiaAssignee: bugsquad => tmb
I'm afraid this is an issue to take upstream to coreutils. If there is an appropriate patch from usptream or applied on another major distro I'd be happy to look at it, but otherwise this is just the behaviour of df... I'm not saying I disagree with you, but really, there is little we can do here at a distro level as I doubt very much anyone wants to write an maintain a local patch unless it's endorsed and sanctioned upstream first.
Sorry, but this bug saw no action since over 2 yrs ago. No cauldron package has stayed the same since then. Closing as OLD Please reopen if this report is still valid for _current_ cauldron and/or fully updated Mageia 4
Status: NEW => RESOLVEDCC: (none) => marja11Resolution: (none) => OLD