[Bug 1740416] [NEW] nfs and cifs mounts are attempted too early in boot process

Thu Dec 28 17:54:19 UTC 2017

Public bug reported:

Systemd should automatically wait for networking and DNS systems to be
in place prior to attempting to mount CIFS or NFS filesystems. This was
the behavior under Ubuntu 17.04. After upgrading to 17.10 the behavior
changed.  Systemd no longer waits for networking and DNS to be
initialized before attempting to mount network filesystems. This
requires me to manually mount these systems or add a hack in the
rc.local file.

Adding _netdev to the fstab entry does not change the incorrect
behavior.  Here is the example that worked under 17.04 but no longer
works under 17.10:

drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs async,proto=tcp 0
0

I also tried:

drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs
_netdev,async,proto=tcp 0 0

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 28 12:44:04 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-12-23 (370 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Gigabyte Technology Co., Ltd. Default string
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=f8d7b91b-a6a4-4ead-a69c-d6249fc9b9ed ro quiet splash
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/docker.service → /etc/systemd/system/docker.service.d/override.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf

 3 overridden configuration files found.
UpgradeStatus: Upgraded to artful on 2017-12-28 (0 days ago)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F24
dmi.board.asset.tag: Default string
dmi.board.name: X99P-SLI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1740416

Title:
  nfs and cifs mounts are attempted too early in boot process

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd should automatically wait for networking and DNS systems to be
  in place prior to attempting to mount CIFS or NFS filesystems. This
  was the behavior under Ubuntu 17.04. After upgrading to 17.10 the
  behavior changed.  Systemd no longer waits for networking and DNS to
  be initialized before attempting to mount network filesystems. This
  requires me to manually mount these systems or add a hack in the
  rc.local file.

  Adding _netdev to the fstab entry does not change the incorrect
  behavior.  Here is the example that worked under 17.04 but no longer
  works under 17.10:

  drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs async,proto=tcp
  0 0

  I also tried:

  drobo5n:/mnt/DroboFS/Shares/PublicNFS /mnt/drobo5n nfs
  _netdev,async,proto=tcp 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 28 12:44:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-12-23 (370 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=f8d7b91b-a6a4-4ead-a69c-d6249fc9b9ed ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/docker.service → /etc/systemd/system/docker.service.d/override.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user at .service → /lib/systemd/system/user at .service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: Upgraded to artful on 2017-12-28 (0 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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