Mailinglist Archive: opensuse-bugs (4687 mails)

< Previous Next >
[Bug 579944] NFS shares cause boot up time to grow exponentially
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 25 Feb 2010 20:00:24 +0000
  • Message-id: <20100225200024.410DF24551B@xxxxxxxxxxxxxxxxxxxxxx>

Neil Brown <nfbrown@xxxxxxxxxx> changed:

What |Removed |Added
CC| |nfbrown@xxxxxxxxxx
Component|Bootloader |Installation
AssignedTo|nfbrown@xxxxxxxxxx |bnc-team-screening@xxxxxxxx
| |

--- Comment #8 from Neil Brown <nfbrown@xxxxxxxxxx> 2010-02-25 20:00:23 UTC ---
I doubt this is related to rpc.idmapd.
Immediately after starting rpc.idmapd, /etc/init.d/nfs attempted to mount
any NFS filesystems required by /etc/fstab.

If, as you say, networking is not configured at this point, then this is going
to fail, and take quite a long time in failing. 3-4 minutes per mount point
does not seem at all unlikely.

- Add the 'bg' option to all the mounts. This will cause them to timeout
significantly more quickly, and continue retrying in the background.
- Don't use network manager, but rather use ifup to configure at boot time.
I appreciate that this might not be practical on a notebook.
- configure automounting to mount those 5 filesystems. That was the mount
wont even be attempted until you want to look a the content.

automounting is really the best option to use in conjunction with

Possibly the yast installer should not allow you to both choose network
manager and request nfs filesystems to be mounted at boot-time.

So I'm treating this as a configuration error, and reassigning to the
installer team so they can comment on whether or not it is possible to
make that error impossible with yast.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >