touch-packages team mailing list archive

[Ronald van der Meer <ronald@xxxxxxxxxxxxx>]

Public bug reported:

Description:	Ubuntu 14.04.3 LTS
Release:	14.04
coreutils:
  Installed: 8.21-1ubuntu5.1
  Candidate: 8.21-1ubuntu5.1
  Version table:
 *** 8.21-1ubuntu5.1 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     8.21-1ubuntu5 0
        500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

It seems like df only shows one nfs mountpoint while more are mounted.

root@klondike:~# mount | grep nfs
192.168.1.2:/volume1/test1 on /test1 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
192.168.1.2:/volume1/test2 on /test2 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
192.168.1.2:/volume1/test3 on /test3 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
192.168.1.2:/volume1/test4 on /test4 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)

root@klondike:~# df -h | grep ^192.168.1.2
192.168.1.2:/volume1/test2  8.1T  1.4T  6.8T  17% /test2

root@klondike:~# cat /etc/fstab | grep ^192.168.1.2
192.168.1.2:/volume1/test1 /test1 nfs vers=4,auto 0 0
192.168.1.2:/volume1/test2 /test2 nfs vers=4,auto 0 0
192.168.1.2:/volume1/test3 /test3 nfs vers=4,auto 0 0
192.168.1.2:/volume1/test4 /test4 nfs vers=4,auto 0 0

root@klondike:~# cat /proc/mounts  | grep ^192.168.1.2
192.168.1.2:/volume1/test1 /test1 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
192.168.1.2:/volume1/test2 /test2 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
192.168.1.2:/volume1/test3 /test3 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
192.168.1.2:/volume1/test4 /test4 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0

** Affects: coreutils (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1495711

Title:
  df only shows one mountpoint

Status in coreutils package in Ubuntu:
  New

Bug description:
  Description:	Ubuntu 14.04.3 LTS
  Release:	14.04
  coreutils:
    Installed: 8.21-1ubuntu5.1
    Candidate: 8.21-1ubuntu5.1
    Version table:
   *** 8.21-1ubuntu5.1 0
          500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
          500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
          100 /var/lib/dpkg/status
       8.21-1ubuntu5 0
          500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  It seems like df only shows one nfs mountpoint while more are mounted.

  root@klondike:~# mount | grep nfs
  192.168.1.2:/volume1/test1 on /test1 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test2 on /test2 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test3 on /test3 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test4 on /test4 type nfs (rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)

  root@klondike:~# df -h | grep ^192.168.1.2
  192.168.1.2:/volume1/test2  8.1T  1.4T  6.8T  17% /test2

  root@klondike:~# cat /etc/fstab | grep ^192.168.1.2
  192.168.1.2:/volume1/test1 /test1 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test2 /test2 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test3 /test3 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test4 /test4 nfs vers=4,auto 0 0

  root@klondike:~# cat /proc/mounts  | grep ^192.168.1.2
  192.168.1.2:/volume1/test1 /test1 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
  192.168.1.2:/volume1/test2 /test2 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
  192.168.1.2:/volume1/test3 /test3 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0
  192.168.1.2:/volume1/test4 /test4 nfs4 rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2 0 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1495711/+subscriptions