[Bug 862928] Re: NFS filesystems are not exported after booting

Clint Byrum clint at fewbar.com
Fri Sep 30 05:51:21 UTC 2011


Hi John, man, sounds like you've been through the ringer on this one.

First off, if you have a truly static network connection that you always
expect to be up on boot, I suggest using /etc/network/interfaces to
define it. As of 11.10, the system will actually delay entering runlevel
2 (a.k.a. 'multiuser' mode) until all of these network interfaces are
up. For earlier releases, one must modify /etc/init/rc-sysinit.conf to
delay until the desired interface is up.

If you have a dynamic connection, things get trickier. I think there may
be a solution here that has very little to do with upstart. When
network-manager brings up interfaces, it looks in /etc/network/if-up.d
and runs all those scripts for each interface. So the nfs-kernel-server
package can add one of these which runs 'exportfs -a' each time an
interface is brought up.

I really don't think its viable to involve bind9 or resolvconf in this
situation. That is completely orthogonal to the issue of NFS not being
able to export all of its exports because the network is not available.

Given all of that, I'm going to redirect this bug task to the nfs-utils
package, as upstart really doesn't have anything to do with this
particular issue.

Also I'm closing the upstream task. There's no deficiency in upstart
itself that has been described here.

** Changed in: upstart
       Status: New => Invalid

** Package changed: upstart (Ubuntu) => nfs-utils (Ubuntu)

** Changed in: nfs-utils (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- NFS filesystems are not exported after booting
+ NFS filesystems are not exported after booting when NetworkManager managed interfaces are needed for DNS resolution

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

Title:
  NFS filesystems are not exported after booting when NetworkManager
  managed interfaces are needed for DNS resolution

Status in Upstart:
  Invalid
Status in “nfs-utils” package in Ubuntu:
  New

Bug description:
  I have an 11.04 Natty system that was upgraded from earlier releases.
  It exports several filesystems via NFSv3 for use by other machines on
  the local network.  When I boot the machine, those filesystems are not
  exported by default.

  Immediately after logging in after a reboot, I can get a terminal and
  run "showmount -e", which shows no filesystems exported.  If I then
  run "sudo exportfs -rv", it exports them without trouble.

  The problem is that it doesn't do this by default.  E.g. after a
  powerfail, it won't restart by providing the filesystems; I have to
  export them manually!  What good is a server that doesn't serve?

  In investigating other bugs relating to network service startup, I
  thought the problem might be that it tries to export to these hosts
  before DNS is available.  So I installed bind9 and made it a secondary
  server for the relevant domains.  Thus, it should be able to resolve
  domain names even before the network comes up.  That didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/862928/+subscriptions




More information about the foundations-bugs mailing list