On Fri, May 13, 2016 at 2:41 PM, Stephen Berg (Contractor)
<[log in to unmask]> wrote:
>
> Mount points that are available on the local hardware under /export/home/
> *AND* through the automounter under /home/ show up under /home/ when they
> should be showing up under their actual mount point, /export/home/.
>
> It seems that df is preferring whichever mount point is shorter. Which seems
> extremely arbitrary and rather stupid.


The kernel doesn't differentiate between the mount of a filesystem and
any of its bind-mounts, so the df developers chose to show the one
with the shortest mount point with "df" and all with "df -a" :


root@west:~# df | grep sda
/dev/sda1 237274808 23197772 202001056 11% /


root@west:~# mount -o bind / /mnt


root@west:~# df | grep sda
/dev/sda1 237274808 23197772 202001056 11% /

root@west:~# df -a | grep sda
/dev/sda1 237274808 23197772 202001056 11% /
/dev/sda1 237274808 23197772 202001056 11% /mnt

root@west:~# grep sda /proc/self/mounts
/dev/sda1 / ext4 rw,relatime,data=ordered 0 0
/dev/sda1 /mnt ext4 rw,relatime,data=ordered 0 0

root@west:~# grep sda /proc/self/mountinfo
24 0 8:1 / / rw,relatime shared:1 - ext4 /dev/sda1 rw,data=ordered
137 24 8:1 / /mnt rw,relatime shared:1 - ext4 /dev/sda1 rw,data=ordered


In your case, is "/home" bind-mounted or nfs-mounted? If it's
nfs-mounted, is the df invocation including "-l"?