Re: 22: nfs = long boot delay

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Aug 14, 2014 at 2:25 PM, Felix Miata <mrmazda@xxxxxxxxxxxxx> wrote:
> On 2014-08-14 12:36 (GMT-0700) Andrew Lutomirski composed:
>
>
>> J. Bruce Fields wrote:
>
>
>>> On Tue, Aug 12, 2014 at 12:58:13AM -0400, Felix Miata wrote:
>
>
>>>> Why when nothing is automounting nfs either as client or server does
>>>> boot
>>>> not proceed to completion without a 2+ minute pause while nfs-server
>>>> fails
>>>> to start?
>
>
>>> Sounds like a bug.  Is the failure to start expected?
>
>
> Not expected by me.
>
>
>> I wonder whether https://bugzilla.redhat.com/show_bug.cgi?id=1129425 is
>> related.  It's possible for nfs client mounts to start a copy of rpc.statd
>> that systemd doesn't know about.
>
>
> I can't tell whether that's related or not. The only significant NFS problem
> I can remember before this, once I originally figured out what little I
> needed to figure out about NFS eons ago when setting up a LAN for the first
> time, had to do with rpcbind replacing portmap.

If you wait long enough for boot to finish, and you do:

# ps -A |grep rpc
# systemctl status nfs-lock

you might get a hint.

--Andy
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux