bug#22199: Bug in coreutils for Linux Mint?? Package coreutils_8.21-1ubu
From:
Dave
Subject:
bug#22199: Bug in coreutils for Linux Mint?? Package coreutils_8.21-1ubuntu5.3_amd64
Date:
Mon, 21 Dec 2015 16:13:12 -0600
User-agent:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
On 12/18/2015 4:28 AM, PƔdraig Brady wrote:
On 18/12/15 00:23, Dave wrote:
df's output shows this on a standard run(df with no flags):
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1953632 4 1953628 1% /dev
tmpfs 400436 1216 399220 1% /run
/dev/sda1 957218452 302330152 606241340 34% /
none 4 0 4 0% /sys/fs/cgroup
none 5120 0 5120 0% /run/lock
none 2002168 8 2002160 1% /run/shm
none 102400 4 102396 1% /run/user
/dev/sdb1 957218452 302510240 606061252 34% /mnt/bkup/device2
But when I mount an external USB disk that's on /dev/sdc1, df shows this
output:
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1953632 4 1953628 1% /dev
tmpfs 400436 1272 399164 1% /run
/dev/sdc1 957218452 302334136 606237356 34% /
none 4 0 4 0% /sys/fs/cgroup
none 5120 0 5120 0% /run/lock
none 2002168 8 2002160 1% /run/shm
none 102400 4 102396 1% /run/user
/dev/sdb1 957218452 302498156 606073336 34% /mnt/bkup/device2
/dev/sdc1 957218452 302564064 606007428 34% /mnt/bkup/externaldevice
The filesystem of "/" has mysteriously changed (in appearance) to
/dev/sdc1?! All I did was mount the /dev/sdc1 device. In fact,
/dev/sdc1 is ONLY mounted at /mnt/bkup/externaldevice, and the mounted
filesystem on "/" is still /dev/sda1. I tested by writing a couple of
files, plus mount shows the correct info:
/dev/sda1 on / type ext4 (rw,errors=remount-ro)
/dev/sdb1 on /mnt/bkup/device2 type ext4 (rw)
If I unmount /mnt/bkup/externaldevice, df still shows /dev/sdc1 as the
"/" filesystem for a small amount of time (10-20 seconds) and then it
goes back to the correct filesystem of /dev/sda1.
What is going on?? This only happened after upgrading to the package of
coreutils mentioned in the subject, it was not doing this previously.
Also, to note, the first two lines of the df output regarding udev and
tmpfs did not appear until this version either. I did see in the
changelog that df was updated to display some additional information, so
perhaps it has to do with that??
I see that ubuntu has backported _some_ patches from master.
Perhaps they were incomplete. Could you please try out this latest df binary.
wget http://www.pixelbeat.org/cu/df
chmod a+x df
./df
(There is a df.sig file is the same dir for gpg verification
using the public key associated with this email address if desired)
cheers,
PƔdraig.
PƔdraig, thanks for the response. The df you provided (v8.24.113-84fcb)
also shows /dev/sdc1 in place of /dev/sda1 once the /dev/sdc1 device is
mounted, the same as in the example in the correspondence above. Is that
what you were expecting?
I found a copy of the old df that was in use before the coreutils
package upgrade, and it presents as version 8.21 just like the current
one when running df --version. The package the original came from was
coreutils_8.21-1ubuntu5.1_amd64 and the df executable is dated Jan 13,
2015. I just ran THAT df, and here's the output (with the /dev/sdc1
device mounted):
So, 2 things of note: 1) I was clearly incorrect in saying in my
original message that the udev and tmpfs lines weren't showing in the
original df listing, because there they are, they were just in a
different spot (ie, not at the top) as you can see above. Apologies for
the misinformation on that. 2) Well, you can see that the old df is
reporting the root filesystem as /dev/sda1 correctly. If I run your df,
or the newer df, both incorrectly show "/dev/sdc1" for the root
filesystem after /dev/sdc1 is mounted at /mnt/bkup/externaldevice.
Also, here are the relevant lines from /proc/mounts and
/proc/self/mountinfo you had requested:
Also, it should be noted, upon looking further into the uuid for "/"
referenced in /proc/self/mountinfo, I found that that reference is
softlinked to "/dev/sdc1" and it stays that way even after the external
device is unmounted. Hmm. So /proc/self/mountinfo seems wrong about "/"
in this case, since it's not referencing /dev/sda in any way. And it's
odd that the older df works, even despite that issue. Maybe I'm not
clear on what all /proc/self/mountinfo is supposed to convey? And maybe
this bug is originating somewhere else outside of df then?