Hi, I'm building custom Fedora remix with some packages from RPMFusion and updated Fedora packages. Last Live USB image I created booted really slow (over 5 minutes). I tracked down the issue to nfs service. Even when this ISO image is used for installing Fedora to HDD the same issue is present.
After stopping nfs service boot time was around 30 seconds!
Did anybody else experience this issue?
Cheers.
Valent Turkovic wrote:
Hi, I'm building custom Fedora remix with some packages from RPMFusion and updated Fedora packages. Last Live USB image I created booted really slow (over 5 minutes). I tracked down the issue to nfs service. Even when this ISO image is used for installing Fedora to HDD the same issue is present.
After stopping nfs service boot time was around 30 seconds!
Did anybody else experience this issue?
If you're seeing long NFS resolution times on boot, check to see if you're running NetworkManager as opposed to the classic network startup. NM is designed to be a per-user thing and isn't started until the desktop user logs in. Nothing dependent on the network will work (including NFS resolution) until that user logs in.
If your boot requires an NFS volume to satisfy your /etc/fstab requirements, then either put an entry in your /etc/hosts file that corresponds to the NFS server or make sure the /etc/fstab entry uses IP addresses and not FQDNs to specify the volume to mount, e.g.
1.2.3.4:/export
and NOT
server.mydomain.com:/export ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Programmers often confuse Halloween and Christmas. - - After all, 31 Oct is the same as 25 Dec! - ----------------------------------------------------------------------
On Wed, 30 Sep 2009 10:03:25 -0700 Rick Stevens wrote:
If your boot requires an NFS volume to satisfy your /etc/fstab requirements
I really, really, wish there was an fstab option I could add to nfs files that said: "Hey Mr. Mounter - when you go to mount this, just background it immediately, don't wait."
That would make it much more convenient to have entries in fstab for nfs mounts to systems which may or may not actually be up at the time I'm booting.
On Wed, 30 Sep 2009, Tom Horsley wrote:
On Wed, 30 Sep 2009 10:03:25 -0700 Rick Stevens wrote:
If your boot requires an NFS volume to satisfy your /etc/fstab requirements
I really, really, wish there was an fstab option I could add to nfs files that said: "Hey Mr. Mounter - when you go to mount this, just background it immediately, don't wait."
That would make it much more convenient to have entries in fstab for nfs mounts to systems which may or may not actually be up at the time I'm booting.
bg
If the first NFS mount attempt times out, retry the mount in the background. After a mount operation is backgrounded, all subsequent mounts on the same NFS server will be backgrounded immediately, without first attempting the mount. A missing mount point is treated as a timeout, to allow for nested NFS mounts.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================
On Wed, 30 Sep 2009 13:40:47 -0400 (EDT) Robert P. J. Day wrote:
bg
If the first NFS mount attempt times out
The problem is the "if the first attempt times out" part. If the machine is down, it is gonna timeout, and each filesystem from that machine is gonna take the same amount of time to timeout. I want the option that says "just background the dadgum thing to start with!"
On Wed, 30 Sep 2009, Tom Horsley wrote:
On Wed, 30 Sep 2009 13:40:47 -0400 (EDT) Robert P. J. Day wrote:
bg
If the first NFS mount attempt times out
The problem is the "if the first attempt times out" part. If the machine is down, it is gonna timeout, and each filesystem from that machine is gonna take the same amount of time to timeout. I want the option that says "just background the dadgum thing to start with!"
good point. i might start with "-F" mount option:
"Fork off a new incarnation of mount for each device. This will do the mounts on different devices or different NFS servers in parallel. This has the advantage that it is faster; also NFS timeouts go in parallel. A disadvantage is that the mounts are done in undefined order. Thus, you cannot use this option if you want to mount both /usr and /usr/spool."
at least that will speed things up.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================
Tom Horsley wrote:
On Wed, 30 Sep 2009 10:03:25 -0700 Rick Stevens wrote:
If your boot requires an NFS volume to satisfy your /etc/fstab requirements
I really, really, wish there was an fstab option I could add to nfs files that said: "Hey Mr. Mounter - when you go to mount this, just background it immediately, don't wait."
There is. Read below.
That would make it much more convenient to have entries in fstab for nfs mounts to systems which may or may not actually be up at the time I'm booting.
Have you tried the "bg" option for the entry in /etc/fstab? I might even suggest "bg,soft":
server:/export /mountpoint nfs options,bg,soft 0 0
or
1.2.3.4:/export /mountpoint nfs options,bg,soft 0 0
Replace "options" with your list of options and tack on ",bg,soft" as I've shown. "man 5 nfs" for details. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer ricks@nerd.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Never try to outstubborn a cat. - ----------------------------------------------------------------------
On Wed, 30 Sep 2009 10:03:25 -0700, Rick Stevens wrote:
If you're seeing long NFS resolution times on boot, check to see if you're running NetworkManager as opposed to the classic network startup.
I'll check, but the point is that I didn't change .ks scripts and previous ISO images booted fast, only the latest ISO images that I created are booting slowly.
That is why I'm asking has anybody seen this and what change could produce this?
On Thu, 2009-10-01 at 16:50 +0000, Valent Turkovic wrote:
On Wed, 30 Sep 2009 10:03:25 -0700, Rick Stevens wrote:
If you're seeing long NFS resolution times on boot, check to see if you're running NetworkManager as opposed to the classic network startup.
I'll check, but the point is that I didn't change .ks scripts and previous ISO images booted fast, only the latest ISO images that I created are booting slowly.
That is why I'm asking has anybody seen this and what change could produce this?
I don't know if this has anything to do with your situation, but the fedora developers list has a thread entitled "Buyer Beware: A Major Change in NFS is about to happen."
Disclaimer: I haven't read the thread. I am not using an NFS mount right now.
I used an nfs mount a few years ago and it too mounted very slowly. I know I fixed it but I can't remember how. Seems to me the mount process (in fstab) could take an option which affected things.
The other thing to look for is version issues between the client and the host in nfs and the other protocols used to implement nfs.
Hope this helps.
-
linux guy -
Rick Stevens -
Robert P. J. Day -
Tom Horsley -
Valent Turkovic