From: NeilBrown <neilb@suse.com>
To: james harvey <jamespharvey20@gmail.com>,
Steve Dickson <SteveD@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfs-server (v4.x only) takes extra 6 minutes to start without rpcbind
Date: Wed, 12 Oct 2016 17:25:23 +1100 [thread overview]
Message-ID: <87lgxu13u4.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CA+X5Wn7CFa9uCZPQZbB0aNs+gXf-CHaaEg5pNpTxWv=iVS+QkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1632 bytes --]
On Sat, Sep 03 2016, james harvey wrote:
>
> FWIW, after nfs-server eventually starts, systemctl still shows
> rpcbind.socket (and rpcbind.service) as masked, inactive, and dead.
I think this is a kernel bug. You can fix it by reverting
Commit: 4b0ab51db32e ("SUNRPC: xs_sock_mark_closed() does not need to trigger socket autoclose")
See also http://www.spinics.net/lists/linux-nfs/msg59264.html and
follow-ups.
>>>
>>> # rpc.mountd --foreground -N 2 -N 3
>>>
>>> {{{ another tty }}}
>>> # strace rpc.nfsd --debug -N 2 -N 3 8
>>>
>>> Gives the attached strace output, which shows the same two really long
>>> delays when reading or writing /proc/fs/nfsd/portlist.
>>>
>> I don't see the attachment...
>>
>> steved.
>
> Strange, wonder if the list removed it - I do see it on my sent message.
>
> Anyways, I just uploaded it here: http://pastebin.ca/3709748
>
> The delays happen at lines 145-149, which print as one line, I just
> broke it apart showing the characters that show on the line before and
> after the delay.
The delay at 'read' is waiting for nfsd_mutex. Probably something else
was trying to start up nfsd and hit the 3 minute wait while writing the
threads. Maybe you interrupted that or backgrounded it or something.
>
> Same at lines 166-170.
This one is the real problem. Starting nfsd tries to register with
rpcbind (even for v4-only) and (due to the bug) it takes 3 minutes to
timeout.
NeilBrown
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]
prev parent reply other threads:[~2016-10-12 6:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 11:22 nfs-server (v4.x only) takes extra 6 minutes to start without rpcbind james harvey
2016-09-02 0:50 ` james harvey
2016-09-03 0:38 ` Steve Dickson
2016-09-03 2:55 ` james harvey
2016-10-12 6:25 ` NeilBrown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgxu13u4.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=SteveD@redhat.com \
--cc=jamespharvey20@gmail.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).