mount -t nfs delayed

[Felix Miata]

Adam Williamson composed on 2014-10-20 17:28 (UTC-0700):

> On Mon, 2014-10-13 at 22:05 -0400, Felix Miata wrote:

>> Adam Williamson composed on 2014-07-29 10:13 (UTC-0700):

>> > On Mon, 2014-07-28 at 13:07 -0400, Felix Miata wrote:

>> >> Ping? Still happening in f21 and Rawhide, but not Cauldron or Factory. :(

>> > Sorry, I'm not seeing anything like it with my NFS mounts.

>> Are all yours done manually rather than on boot, via alias that does four mount points, as are mine?

> No, I use systemd auto-mounting.

> ircproxy:/	/share/irclogs	nfs	noauto,user,comment=systemd.automount	0 0

>> > You'd probably best file a bug.

>> Maybe figure out first if one already exists, and what would go in it?

> Well, I'd start out by describing the problem and attaching the journal
> and the fstab lines and the enable/disable state of the relevant
> services.

I may have narrowed down the problem to this:

13 working installations:
rpcbind.service                         enabled

14 broken installations:
rpcbind.service                         static

All those working do not have NetworkManager installed. Half those not
working have NetworkManager installed.

On a broken one (host g5eas 32 bit F21, which was and is broken, had
NetworkManager installed before I removed it minutes ago, and remains broken)
I get the following:
systemctl status rpcbind on first login:
* rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: inactive (dead)
systemctl status rpcbind after ifup eth0:
* rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: inactive (dead)
systemctl status rpcbind after nfs mount attempts:
* rpcbind.service - RPC bind service
   Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
   Active: active (running) since Tue 2014-10-21 00:52:11 EDT; 1min 39s ago
  Process: 795 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited,
status=0/SUCCESS)
 Main PID: 800 (rpcbind)
   CGroup: /system.slice/rpcbind.service
           --800 /sbin/rpcbind -w

Oct 21 00:52:11 g5eas rpcbind[795]: cannot create socket for udp6
Oct 21 00:52:11 g5eas rpcbind[795]: cannot create socket for tcp6
Oct 21 00:52:11 g5eas systemd[1]: Started RPC bind service.

journalctl -xn after above:
-- Logs begin at Sat 2014-03-22 16:16:21 EDT, end at Tue 2014-10-21 00:53:11
EDT. --
Oct 21 00:52:43 g5eas systemd[1]: Started Session 2 of user root.
-- Subject: Unit session-2.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-2.scope has finished starting up.
--
-- The start-up result is done.
Oct 21 00:52:43 g5eas login[479]: pam_unix(login:session): session opened for
user root by LOGIN(uid=0)
Oct 21 00:52:43 g5eas login[479]: ROOT LOGIN ON tty2
Oct 21 00:53:11 g5eas rpc.statd[794]: failed to create RPC listeners, exiting
Oct 21 00:53:11 g5eas systemd[1]: rpc-statd.service: control process exited,
code=exited status=1
Oct 21 00:53:11 g5eas systemd[1]: Failed to start NFS status monitor for
NFSv2/3 locking..
-- Subject: Unit rpc-statd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit rpc-statd.service has failed.
--
-- The result is failed.
Oct 21 00:53:11 g5eas systemd[1]: Unit rpc-statd.service entered failed state.
Oct 21 00:53:11 g5eas systemd[1]: rpc-statd.service failed.
Oct 21 00:53:11 g5eas rpc.statd[850]: Version 1.3.0 starting
Oct 21 00:53:11 g5eas rpc.statd[850]: Flags: TI-RPC

Before filing any bug I'd like to make more progress to get an idea if there
actually is any bug, but am not sure where to look in order to make more
progress. Systemctl enable rpcbind does not make a change from static to
enabled. There is no man page for rpcbind.service. Man rpcbind doesn't look
helpful. Man systemctl is a zoo. I've no recollection how networking ever got
to work on the installations that do not have NetworkManager, though I
suppose that could be fallout from always doing HTTP installations in the
first place. System-config-network didn't provide any improvement.

More detail in data/logs collected since Saturday:
http://fm.no-ip.com/Tmp/Linux/F/NFS/

Still think I should file a bug already? Any suggestions how to proceed
further (first?)?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/