Not to pile on here . . . but i have three servers 13.04 at Rackspace
(admittedly, I cannot be certain that the actual hardware is anything
like identical -- but I have configured them side-by-side, and their
installation is identical).  Two of the three servers can handle two (2)
NFS mounts in the /etc/fstab during boot.  The third one can only handle
one (1).  It appears that which one is unimportant, since I can swap the
mounts around, reconfigure them, etc.  But if there are two in the
/etc/fstab for the one server, it sticks at "disconnected from
Plymouth."

My solution was to put the "most important" nfs mount in the /etc/fstab,
and to put others in /etc/rc2.d.  But that's me.  This certainly *seems*
to be a race condition, but I cannot offer anything more than my opinion
on that.  Perhaps this extra observation helps, or perhaps you can
ignore it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1226766

Title:
  Mountall fails to mount NFS partitions on boot with GigE network
  managed by NM

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  NFS partitions fail to mount on boot, and mountall freezes without mounting 
them. If I revert this change to the init script:
       . /etc/default/rcS || true
       [ -f /forcefsck ] && force_fsck="--force-fsck"
       [ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix"

  + # Doesn't work so well if mountall is responsible for mounting /proc, heh.
  + if [ -e /proc/cmdline ]; then
  + for arg in $(cat /proc/cmdline); do
  + case $arg in
  + -q|--quiet|-v|--verbose|--debug)
  + debug_arg=$arg
  + ;;
  + esac
  + done
  + fi
       # set $LANG so that messages appearing in plymouth are translated
       if [ -r /etc/default/locale ]; then
           . /etc/default/locale || true
           export LANG LANGUAGE LC_MESSAGES LC_ALL
       fi

  - exec mountall --daemon $force_fsck $fsck_fix
  + exec mountall --daemon $force_fsck $fsck_fix $debug_arg
   end script

  it works. It seems strange that this would stop NFS from mounting on boot. It 
appears that the NFS mounts are occurring before DNS is up. mountall.log 
contains:
  mount.nfs: Failed to resolve server rt-ac66u: Name or service not known
  mountall: mount /mnt/readyshare [815] terminated with status 32
  Filesystem could not be mounted: /mnt/readyshare
  mountall: Disconnected from Plymouth

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: mountall 2.51
  Uname: Linux 3.11.1-customatom x86_64
  NonfreeKernelModules: nvidia
  .run.mount.utab:
   
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  Date: Tue Sep 17 14:49:53 2013
  ExecutablePath: /sbin/mountall
  InstallationDate: Installed on 2012-04-15 (520 days ago)
  InstallationMedia: Mythbuntu 12.04 "Precise Pangolin" - Beta amd64 (20120328)
  MarkForUpload: True
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.1-customatom 
root=UUID=708b3ba8-c42a-4adf-a195-c0fb8d8f8dd3 ro --verbose
  SourcePackage: mountall
  UpgradeStatus: Upgraded to saucy on 2013-06-28 (81 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226766/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to